Topsort Events Destination

This destination helps you track the 3 main events Topsort needs to serve the most relevant ads and accomplish attribution for sponsored listings: impressions, clicks and purchases. Here is an explanation of what each one of these means to Topsort:

• Impression: Every time a user sees a promoted product in a listing page (PLP) or section, you should trigger an impressions event.
• Click: If the user then clicks or adds the promoted product to a cart, you should trigger a click event.
• Purchase: When an order is completed and confirmed to be successful, report a purchase event to Topsort. You can report a purchase whether it has promoted products or not. Topsort takes care of filtering relevant promoted products inside the completed order given the information about promoted clicks.

This destination has 3 default presets that map the Track events 'Product Viewed', 'Product Clicked' and 'Order Completed' to Topsort's impression, click and purchase events, respectively. If you're not familiar with the Segment Spec, take a look to understand what the Track method does.

The mappings in the Topsort destination are built based on the Segment Ecommerce Spec. If you have different Segment Track events mapped to these action definitions, then Topsort can adapt this destination to your case. Once the destination is configured, activate only the mappings relevant to your site. See point 5 of the set up for more details.

1. From the Segment web app, click Catalog, then click Destinations.
2. Search for "Topsort" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the Topsort Manager Platform, go to Settings > API Integration to find or create your Marketplace API Key for auctions and events.
4. Return to the Topsort destination in the Segment app and enter the value for your Marketplace API Key.
5. Enable only the Track events relevant to your site and so that the events do not get duplicated with a single user action. For example, if you always trigger a Product Clicked event together with the Product Added event when a user makes a click in the "Add to cart" button, then you should enable only the Product Clicked event for the Topsort Destination.

Topsort has the following presets

Build your own Mappings. Combine supported triggers with the following Topsort-supported actions:

• Purchase
• Click
• Impression
• ImpressionsList
• Page Views

Send purchase events to Topsort when a consumer places an order.

Purchase is a Cloud action. The default Trigger is type = "track" and event = "Order Completed"

Send click events to Topsort when a consumer has clicked on a promotable.

Click is a Cloud action. The default Trigger is type = "track" and event = "Product Clicked"

Send impression events to Topsort when a consumer has viewed a promotable.

Impression is a Cloud action. The default Trigger is type = "track" and event = "Product Viewed"

Send impression events to Topsort when a consumer has viewed a list of promotables.

ImpressionsList is a Cloud action. The default Trigger is type = "track" and event = "Product List Viewed"

Send page view and screen view events to Topsort

Page Views is a Cloud action. The default Trigger is type = "page" or type = "screen"

You don't need to change anything about the way you report Track events to Segment. The only extra field you need to provide, only for the impression and click events, is the resolvedBidId given in the winner promoted product (whether it is from the Auctions API or the proxy response). Please find below an example call to track a product listing page (PLP) click event with the resolvedBidId included:

1
analytics.track("Product Clicked", {
2
  product_id: product.id,
3
  name: product.name,
4
  resolvedBidId: product.resolvedBidId
5
});

For Segment's browser and mobile libraries Topsort recommends that you identify your logged-in users using Segment's Identify method.

Please find an example Identify call below:

1
analytics.identify('361b1fdfbeaa9d64a13c033eb9f970dc6740f6bc', {
2
  email: 'john.doe@example.com'
3
});

Once a user is identified, each call to Segment's Track method automatically records the user ID. Users that are not logged in can be tracked using an anonymousID.

If you use a server-side source please provide one or more identifiers: anonymousId or userId.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Segment lets you change these destination settings from the Segment app without having to touch any code.