Standard campaign metrics like opens and clicks may not fully reflect your business impact. Use custom events to track actions that matter to your goals — such as purchases or subscriptions — and measure them as custom goals. See Custom goals and campaign attribution.
View a custom event
Click any custom event on the clickstream page to view its tracking code, the last recorded event, and any associated event-triggered campaigns.
Add a custom event
Go to Customer Data > Events and click Add a custom event.
Some options appear only after you save and reopen the event. Options marked "contact support" require enablement by support@blueshift.com.
Basic settings
| Field | Description |
|---|---|
| Display name | The label shown across the Blueshift UI — in segmentation, event imports, and campaign setup. |
| Event name | The unique identifier passed in the event field via API or tracking code. Accepted: letters, digits, hyphens, underscores. Max 64 characters. No periods, spaces, or numeric-only names. |
Save products
When enabled, product data in the event payload is saved to the user's profile. Select a saving mode:
| Mode | What it does |
|---|---|
| Replace existing |
Products from the latest event payload replace all existing products. Select how they are replaced:
|
| Append to existing | Products from each event are added to the existing list. Limit: 1,000 products per event per user. |
| Save on timeline | Similar to Append to existing, but products are saved with a timestamp so you can retrieve them by date range. Limit: 1,000 products per event per user. |
Example: how product saving works
A user views three jackets at 2 pm (prod_ids: J1, J2, J3) and three shoes at 4 pm (prod_ids: S1, S2, S3). Here's what Blueshift retrieves for recommendations at 5 pm:
- Replace existing — retrieves S1, S2, S3 only. The jacket views are gone.
- Append to existing — retrieves J1, J2, J3, S1, S2, S3. All views are retained.
- Save on timeline — retrieves J1, J2, J3, S1, S2, S3, but you can filter by time. For example, retrieve only products viewed after 3 pm to get S1, S2, and S3.
Advanced options
| Option | Description |
|---|---|
| Is goal event | Marks this event as a custom goal for campaign attribution. Contact support to enable. See Custom goals and campaign attribution. |
| Event attribution days | Available for goal events only. Sets a custom attribution window. If not set, the account-level default applies (Account settings > Other settings > Attribution days). Example: 1 day for "Video started," 7 days for "Subscription renewed." |
| Enable revenue attribution | Available for goal events only. Calculates revenue from this event using the revenue field in the payload by default. |
| Enable user updates | Allows this event to update user attributes via a backend identify call. Not available for standard events. Contact support to enable. |
| Whitelist attributes for user update | By default, only customer_id, email, cookie, and device_id can update user attributes. Contact support to allow additional attributes. |
| High priority | Routes campaigns linked to this event through a dedicated priority queue. Contact support to enable. |
Comments
0 comments