Community

Twitter has fairly rich APIs that enable marketers to download vast troves of data. Most of this data is not in a format that is easily accessible to Lytics since identifying events would not map to our user profiles. Some marketers make use of Twitter by downloading .csv files of key customer audiences for ad targeting on Twitter. This tactic may make sense for you, reach out to Lytics Support to explore more options.

If you have previously successfully connected a third party tool to Lytics and you discover that integration is no longer importing or exporting. You may try stopping the existing export and starting a new one. If you are not able to set up a new version this is likely because you need to reauthorize.

For the most part, our list of integrations in the Lytics interface reflects most tools we currently integrate with natively. Some integrations work through our Javascript tag and may not be reflected in the interface. Reach out to our support team to check if we have any existing connector with your tool. We can also develop new integrations for customers as part of a service agreement.

Custom integrations help you get data in and out of Lytics when a direct integration is not available.

1. From Data > Integrations in the Lytics interface, select the custom integrations tile.
2. Select Import CSV.
3. Select Use Lytics Managed SFTP Instead.

Lytics is capable of pulling query string parameters out of urls and this can be used to identify your email subscribers on your website when they click through an email link. Each email tool may have a different way of supporting custom values in an email template. As an example, lets look at Mailchimp:

Google Analytics has a limit on the number of characters (bytes) for custom dimensions. It is set at 150 bytes which means if you attempt to pass a group of audiences from Lytics to GA where the total is over 150 characters you will receive a warning (Parameter for Custom Dimension is too long (max 150)) in GA or Google Tag Manager and the audiences will not be received in GA.

Currently, our AWS S3 export operates on full segment scans. This means that each export will contain all users in the selected audiences. Supporting diffs is under consideration for a future enhancement but is not currently available.

The best way to update an authorization is to add a new authorization for the integration that is changing. Lytics Support can help with this transition.

You can verify that data is coming into Lytics by navigating to Data -> Data Streams. The default stream, unless otherwise configured will contain your web data and then you will see your other integrations in the drop down of stream names. Each stream page will show you the last time we received data.