Breadcrumbs

*Event Data Integration: Overview

Symbiosys requires two event-level datasets, which are used for reporting, attribution, and optimization:

  • page views – visit/click events, includes subsequent page views for web integration

  • orders – purchase events

Event data can be integrated using one or more of the below methods:

  • [Preferred] BigQuery Transfer – Send data directly from your data warehouse (or via GA4) to Symbiosys via BigQuery transfer.

  • [Preferred] File Dump – Send CSV file dumps to Symbiosys via shared cloud storage bucket (e.g., GCS, S3, Azure).

  • Event API Integration – Use the Symbiosys Event API to stream data directly from your site/app to Symbiosys via client- or server-side tag.

High-Level Guidance

To ensure accurate attribution, clean event data, and seamless troubleshooting, follow these best practices when integrating visit and order data:

  • Start early. Event data integration runs independently of feed/channel setup—handling both in parallel ensures a faster launch. Integration and validation may take longer than feed/channel setup, so an early start is key.

  • Track web and app data. While web tracking is the focus in the pilot phase, collecting app data is essential for optimizing performance, especially if most purchases occur in-app.

  • Include all campaign traffic (Symbiosys & non-Symbiosys). Sending event data from all campaigns helps diagnose tracking issues, assess data health, and improve performance evaluation.

  • Ensure full-site tracking. Capture all key page views—not just landing pages and orders—to prevent session mismatches and incomplete attribution.

  • Monitor user/session identifiers. Ensure Visitor IDs persist across sessions and correctly transition to CRM IDs. Conduct internal audits for issues like ID duplication, session-based generation, or bot anomalies, and report any concerns to your Symbiosys SE.

  • Comply with privacy rules. Inform Symbiosys of any tracking restrictions due to user agreements or privacy laws. Symbiosys does not collect PII.

Instructions

  1. Review data requirements.

    1. See POST Endpoint Reference for expected data points*.

  2. Choose an integration method.

    1. See Methods & Data Sources to determine the best approach.

  3. Ensure complete and accurate user/event coverage.

    1. See Ensuring Accurate Tracking & Data Integrity for user/event tracking guidance.

  4. Integrate Using Your Chosen Method(s).

  5. Validate event data integration.

    1. Work with your Symbiosys SE to validate and fine-tune the integration.

*The example requests in the POST Endpoint Reference contain parameter requirements that are specific to the Event API, including your public API key. You will not require a key if integrating via data dump or direct transfer. However, independent of integration method, your event data should contain all other fields in the expected format