*Event Data Integration: Ensuring Accurate Tracking & Data Integrity

Our minimum requirement is to collect landing page views (click-throughs) and order events. However, to ensure consistent data quality, accurate attribution, and seamless troubleshooting, please ensure event tracking is as comprehensive. Our ingested dataset should essentially mirror the data collected by your target ad channel. Additionally, ensuring user identifiers (Visitor ID & CRM ID) are correctly assigned and maintained is essential to prevent misattribution, duplicate orders, and inaccurate reporting.

Comprehensive Tracking Requirements

• Client- or server-side tag on your site/app

  • Load the tag on all page types, not just landing and order confirmation pages. Do not apply restrictive load rules.

• Direct transfer or CSV file dumps

  • If your data source captures subsequent page views between landing page view and purchase, include these in your transfer/dump

• Exception: App data

  • Currently, we only require click-through (app opens with deep link URI) and order events for app data ingestion. No need to send in-app navigations.

• Consideration: User Opt Out

  • Events for users that have opted-out of tracking should still be passed, and flagged with user_opt_out:trueto exclude them from data processing (attribution and performance reporting). Ingestion of opted-out events prevents data fragmentation.

Reasons for Comprehensive Tracking

• More Accurate Attribution

  • Full tracking provides a complete picture of user behavior, reducing the risk of misattributed conversions.

  • If certain pages are excluded, tracking gaps can lead to over- or under-reported sales figures.

• Prevents Data Gaps from User Behavior

  • Users enter the site through various landing pages—not just campaign-specific ones.

  • Ensuring all entry and exit points are tracked prevents incomplete user session data.

• Eliminates Unexpected Tag Behavior & Improves Performance

  • Restrictive tag load rules can cause inconsistent visitor ID tracking, which in turn breaks attribution logic.

  • Ensuring the tag loads everywhere prevents session mismatches and incomplete conversions.

• Ensures Reliable Event Data Validation

  • Full-site tracking allows us to verify that key identifiers (gclid, page views, conversions) are captured correctly.

  • This reduces time spent troubleshooting missing or incorrect data post-integration.

• Minimal Performance Impact

  • Our client-side tag is lightweight (<1 kb), ensuring no noticeable impact on page load speed while significantly improving data integrity.

Ensuring User Identifier Integrity (Visitor ID & CRM ID Tracking)

Beyond full-site tracking, correct user identifier assignment is crucial to prevent attribution errors and to ensure clean event data. A common issue occurs when a single visitor ID is linked to multiple CRM IDs, which can distort reporting. If you’re aware of any nuances in how visitor or CRM IDs are assigned—such as session-based ID generation, customer service representative (CSR) workflows, or account merging rules—please inform us so we can account for these factors and ensure accurate tracking. Below are some common causes of identifier issues:

• Customer Service Representative (CSR) Logins

  • Issue: Some CSR tools allow agents to log in as customers without properly resetting the visitor ID.

  • Impact: This can cause hundreds of customer accounts to appear under a single visitor session, inflating conversion data.

  • Fix: If CSRs frequently place orders for customers, visitor IDs should reset upon login to prevent session contamination.

• Duplicate or Merged CRM Records

  • Issue: CRM systems may create multiple CRM IDs for the same user due to session-based ID generation, data imports, or account duplication.

  • Impact: Users may appear as multiple distinct customers, inflating order volume and misaligning campaign attribution.

  • Fix: Review how visitor IDs persist across sessions and devices to ensure that CRM IDs are assigned correctly.

• Bot or Automated Traffic

  • Issue: Bots, scraping tools, or automated scripts can generate artificial CRM IDs tied to a single visitor ID.

  • Impact: This can lead to unnatural spikes in order volume or user activity, distorting performance metrics.

  • Fix: Conduct traffic analysis to detect bot-like behavior and ensure account creation processes prevent automated duplication.

Observance of Privacy Law

Symbiosys is fully compliant with broader privacy regulations (e.g. GDPR, CCPA, LGPD):

• Symbiosys does NOT request, ingest, process or store PII.

  • Required user fields (visitor ID, CRM ID, hashed email, session ID) are anonymized and can’t be used to personally identify a user.

• Symbiosys does NOT share event data with third parties.

• Symbiosys retains event data for 13 months by default, but this can be adjusted if needed.

Consent-based Tracking

Symbiosys only processes data for users that have not opted out of event tracking. Our data model supports an optional opt-out flag in the user_opt_outfield.

• If user_opt_out:true, the event is ingested, but not processed, meaning it’s excluded from attribution and performance reporting.

• If user_opt_out:true and the click page view URL contains a privacy identifier passed by the target ad channel (e.g., gbraid), Symbiosys defaults to using this this privacy identifier in place of the channel click identifier.

• If user_opt_out:false or its not explicitly passed, the user’s session data is processed normally.

If your user agreement has other tracking stipulations, share these with your Symbiosys SE to ensure we’re in full compliance.