2) Once you’re recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: Account -> Manage Accounts.
You can also enter your Data API Key under Advanced Options. The data API Key can send data to Lytics, but not edit your account info. The Full API Key has access to edit all of your account info, so it should not be used for sending data.
Paste into your Destination page:
You can see what data fields Lytics pulls in by default.
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, Personas 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), Personas sets that value to
When you first create an audience, Personas 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.
Real-time to batch destination sync frequency
Note that real-time audience syncs to Lytics may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
|Allow UID Sharing Across Multiple Domains||
A brief, but informative name for organizating your data in Lytics. Only necessary when you are tracking multiple websites.
This page was last modified: 15 Jul 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!