Standard campaign metrics like opens and clicks might not be sufficient to measure how a marketing campaign is actually impacting your business goals, for example, your topline. At Blueshift, you can add events that represent your topline as custom goals. For more information, see custom goals for campaign attribution.

View a custom event

Click on an individual custom event in the click stream page to view the tracking code, as well as example of last event recorded. You can also view any event triggered campaigns that are associated with this event.


Add a custom event

Click Add a custom event in the click stream page to add a custom event from Blueshift UI. Add the information for the custom event and save.


Note: Some of the fields described are available after you add a custom event and then edit it. Some options can be enabled only by

Display Name The event name displayed in Blueshift on the clickstream page, segmentation, event file imports, campaigns create page, and so on.
Event Attribute The value of event key field during event api calls.
Is Goal Event

You can set up custom goals by marking certain events as "Goal" events. When Blueshift receives these events, it will try to attribute the event (custom goal) to a campaign message based on the attribution settings.

To set an event as a goal event or custom goal, contact

Enable Revenue Attribution

This option is available only for goal events.

Revenue attribution can be enabled for any goal event. When enabled, the revenue generated due to the goal event is calculated. By default, the revenue number is taken from the "revenue" field in the event payload. But it can also be configured to be picked from some other field by setting the "goal_event_revenue_attribute" in the admin settings.

Save Products When enabled, if the event data contains product IDs, these products are saved to the user's profile depending on the Product Saving Mode selected.
  • Replace existing - Products that are sent in the last event payload are saved. All existing products are replaced.
  • Append to existing - Products that are sent in the last event payload are saved. You can save up to last 1000 products per event per user.
  • Save on timeline - Products that are sent in the last event payload are saved on a timeline so that you can retrieve products based on a start and end date range. You can save up to last 1000 products per event per user. 
Enable User Updates

Select to allow the custom event to update the user. An identify call is generated in the backed, which will update the user attributes.

To enable user updates via events, contact

Note: The Enable user updates option is not available for standard events.

Whitelist Attributes for User Update

By default we allow only user identifiers (customer_id, email, cookie, device_id). If you want to allow other event attributes, you would need to whitelist them here.

To whitelist any attribute for events, contact

High priority

Campaigns corresponding to the event are processed at a priority through a dedicated queue.

To use this option, contact



Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.