Troubleshooting

Some duplicate pairs (user_id, event_id) can be expected in the all_events table, as long as the event_table_name value is different for the rows that share an event ID.

If you have two event definitions that overlap, it's possible for a single event with a unique event ID to qualify for multiple event definitions.

Let's say you have two click event definitions: one that captures every click on your platform and one that captures clicks on a specific element. A click event that qualifies for the first event will automatically qualify for the second event because the first event captures any click.

If both event definitions are synced to Data Connect, they will each have their own event table downstream and a single event that qualifies for both definitions will appear on both tables with the same event ID. An event will always have just one event ID, even if it qualifies for multiple event definitions (and by extension, is included on multiple event tables in your data warehouse).

The all_events table is a UNION of every individual event table that has been synced to your data warehouse. If both individual event tables include the same event, then the all_events table will show duplicate event IDs. However, these two rows will have different event_table_name values.

The primary key for all_events should be a composite of user_id, event_id, and event_table_name. In individual event tables, a composite of user_id and event_id should suffice.

We don't currently sync Initial User properties downstream in Data Connect (such as Initial Marketing Channel, or Initial Browser). Refer to how to recreate those properties in your warehouse.

This FAQ applies to using Data Connect for warehouses (Redshift, BigQuery, Snowflake) only.

A given event_id across all tables corresponds with a unique event recorded by Contentsquare. That said, the same event_id may exist in multiple event tables, as Contentsquare provides the flexibility to create multiple event definitions that may correspond to the same raw event. For instance, you may define the following two events in the product:

• Click CTA defined as Click on .cta
• Click CTA - Homepage defined as Click on .cta with a filter where Path equals /

If a user clicks the CTA on the homepage, a new event will be recorded on both event tables that correspond with both event definitions. As a result, two events with the same event_id will be included in the all_events table, as it contains every recorded instance of all defined and custom events.

Additionally, pageviews can share an event_id with a defined event. The defined event with a given event_id will have a unique time, after excluding where event_name = 'pageviews'.