Why do automotive marketers need 400-day attribution windows?

The average vehicle research journey is 90-120 days from first impression to dealership visit, with luxury and EV journeys often longer. Safari ITP's 7-day cookie cap means standard client-side attribution loses the entire signal across this window. 400-day server-set first-party cookies cover the full buying cycle, recovering attribution that gtag.js and Meta Pixel cannot capture.

How does this work for OEM-to-dealer attribution?

OEM brand websites and dealer locator tools share an identity space via cross-domain identity resolution. A buyer who researches on the OEM site, then visits a dealer site, then submits a test-drive request is stitched into a single journey. The dealer attribution flow is captured server-to-server from the dealer's booking system, joining online research to in-person test drives.

Can this handle our connected-car telemetry alongside marketing events?

Yes. Connected vehicle events (ignition, location pings, service alerts) flow through the same server-to-server ingestion as web and app events. The same identity graph stitches a buyer's pre-purchase research to post-purchase ownership behaviour, supporting service marketing, accessory upsell, and customer experience analytics. Privacy controls apply uniformly via the Org Data Layer.

How do we manage data across multiple national markets?

Single-tenant deployment per region (or per OEM brand) means EU customer data lives in EU infrastructure, US in US, with no shared data plane. Per-vendor delivery gates can restrict downstream sharing further (e.g. EU customer events deliver only to EU-region vendor endpoints). Compliant with GDPR, ePrivacy, and the various national data protection regimes that apply to automotive customer data.

How does this support GA4 360 and CAPI for our agency partners?

Server-to-server delivery to GA4 (Measurement Protocol) and Meta CAPI runs from your infrastructure, with hashed PII applied per-vendor in the right format automatically. Agency partners get cleaner data into the platforms they manage, without you sharing raw PII or relying on the agency's client-side tag implementation. Per-pipeline blueprints make it easy to add or remove agency-managed integrations.

Automotive

The test drive started 6 weeks ago. Your cookies expired 5 weeks ago.

Vehicle purchases have the longest digital research cycle in e-commerce. Buyers spend weeks comparing models, configuring options, and visiting dealer sites across multiple devices. Safari's 7-day cookie cap means your attribution data dies long before the customer converts.

6-12 weeks

Average research cycle

Buyers visit 4-6 sites over weeks before a test drive or enquiry

20-40%

Conversions hidden

Ad blockers strip vendor tags on automotive research sites

7 days

Safari cookie limit

ITP expires cookies long before the buyer is ready to act

£30K+

Average transaction value

Every lost attribution point represents significant ad spend

Why automotive attribution is broken

Vehicle research spans weeks, multiple devices, and multiple domains. Client-side tracking was never designed for journeys this long or this complex.

Research outlasts your cookies

Buyers research for 6-12 weeks. Safari deletes your tracking cookies after 7 days. By the time they book a test drive, you have no idea which campaign brought them in.

Cross-device journeys are invisible

Customers research on mobile, configure on desktop, and visit the showroom in person. Without persistent identity, these look like three separate users.

High-value conversions with no visibility

Automotive ad budgets are among the highest in digital. When 30% of conversions are invisible to your attribution, Smart Bidding optimises on incomplete data.

How Signal recovers automotive attribution

Server-set 400-day cookies, persistent cross-device identity, and first-party delivery that survives the entire vehicle research journey.

400-day attribution

Server-set first-party cookies persist for 400 days — covering the entire research, test drive, and purchase cycle. ITP cannot touch them.

Survive the full 6-12 week research window
Attribute test drives back to the original campaign
Track the complete journey from first ad click to purchase

Cross-device identity

Persistent server-side identity links the mobile research session to the desktop configurator visit to the dealer website enquiry — one customer, one journey.

Link mobile research to desktop configuration
Recognise returning visitors across devices
Cross-domain identity for OEM and dealer sites

Better Smart Bidding

When Google Ads and Meta see 100% of your conversions instead of 70%, their algorithms optimise for the customers who actually buy — not just the ones they can see.

Recover 20-40% of hidden conversions for bidding
Enhanced Conversions with SHA-256 hashed PII
Accurate ROAS across the full purchase cycle

Pipeline as Code

From vehicle enquiry to every ad platform

A single vehicle_enquiry event is captured once by the 5.2KB collector, enriched with vehicle model and dealer data, then delivered simultaneously to Google Ads Enhanced Conversions and Meta CAPI with SHA-256 hashed customer data.

Vehicle model, dealer code, and finance type captured automatically
PII hashed before leaving your infrastructure
Consent enforced at collection and delivery
One event, multiple vendor-specific payloads

pipeline/vehicle-enquiry.ymlYAML

# Vehicle Enquiry Pipeline
event: vehicle_enquiry
source: web

org_data_layer:
  schema:
    - field: properties.vehicle_model
      type: string
      required: true
    - field: properties.dealer_code
      type: string
    - field: properties.finance_type
      type: string
  pii:
    - field: context.traits.email
      action: sha256
    - field: context.traits.phone
      action: sha256
  consent:
    required: [analytics, marketing]

pipelines:
  - name: google_ads
    integration: google-ads-enhanced-conversions
    event_name: vehicle_enquiry
    mapping:
      - source: context.traits.email_hash
        target: user_data.sha256_email_address
      - source: properties.vehicle_model
        target: custom_variables.vehicle_model
      - source: properties.dealer_code
        target: custom_variables.dealer_code

  - name: meta_capi
    integration: meta-conversions-api
    event_name: Lead
    mapping:
      - source: context.traits.email_hash
        target: user_data.em
      - source: properties.vehicle_model
        target: custom_data.content_name
      - source: properties.finance_type
        target: custom_data.content_category

Attribution that covers the full buying cycle

Every ad platform claims full credit for every test drive and enquiry. Signal sits between the conversion and every vendor API — you control which platform receives credit with configurable attribution models.

Last Click

Attribute the test drive booking to the final campaign that drove the visit.

First Click

Credit the channel that first introduced the buyer to the brand — weeks before the enquiry.

Time Decay

Weight credit toward recent touchpoints while acknowledging the initial research phase.

Position Based

40/20/40 split — credit both the awareness campaign and the final conversion driver.

Linear

Equal credit across the 6-12 week journey. No channel is invisible.

Custom Rules

Define your own logic — e.g., always credit branded search, split non-brand across touchpoints.

Built for OEM and dealer group complexity

Automotive digital journeys cross domain boundaries constantly — from the OEM brand site to the vehicle configurator to the local dealer website. Signal's cross-domain identity and brand workspaces are designed for exactly this structure.

For OEM brands

Cross-domain identity from brand.com to configurator to dealer sites
Centralised data governance across all dealer group properties
Per-dealer brand workspaces with scoped data access
Unified attribution across the entire purchase funnel

For dealer groups

Single collector across all franchise sites
Per-franchise pipeline configurations
Local ad spend attributed accurately to enquiries and sales
VPC deployment meets manufacturer data requirements

Frequently asked questions

Why do automotive marketers need 400-day attribution windows?: The average vehicle research journey is 90-120 days from first impression to dealership visit, with luxury and EV journeys often longer. Safari ITP's 7-day cookie cap means standard client-side attribution loses the entire signal across this window. 400-day server-set first-party cookies cover the full buying cycle, recovering attribution that gtag.js and Meta Pixel cannot capture.
How does this work for OEM-to-dealer attribution?: OEM brand websites and dealer locator tools share an identity space via cross-domain identity resolution. A buyer who researches on the OEM site, then visits a dealer site, then submits a test-drive request is stitched into a single journey. The dealer attribution flow is captured server-to-server from the dealer's booking system, joining online research to in-person test drives.
Can this handle our connected-car telemetry alongside marketing events?: Yes. Connected vehicle events (ignition, location pings, service alerts) flow through the same server-to-server ingestion as web and app events. The same identity graph stitches a buyer's pre-purchase research to post-purchase ownership behaviour, supporting service marketing, accessory upsell, and customer experience analytics. Privacy controls apply uniformly via the Org Data Layer.
How do we manage data across multiple national markets?: Single-tenant deployment per region (or per OEM brand) means EU customer data lives in EU infrastructure, US in US, with no shared data plane. Per-vendor delivery gates can restrict downstream sharing further (e.g. EU customer events deliver only to EU-region vendor endpoints). Compliant with GDPR, ePrivacy, and the various national data protection regimes that apply to automotive customer data.
How does this support GA4 360 and CAPI for our agency partners?: Server-to-server delivery to GA4 (Measurement Protocol) and Meta CAPI runs from your infrastructure, with hashed PII applied per-vendor in the right format automatically. Agency partners get cleaner data into the platforms they manage, without you sharing raw PII or relying on the agency's client-side tag implementation. Per-pipeline blueprints make it easy to add or remove agency-managed integrations.

Safari ITP Recovery

400-day first-party cookies for the long automotive consideration cycle.

Attribution

Cross-platform attribution that prevents OEM and dealer double-counting.

Mobile SDK

iOS and Android SDKs for OEM brand apps and connected vehicle services.

Identity

Cross-domain identity resolution from OEM site to dealer to app.

Attribute every test drive and enquiry to the right campaign

See how Datafly Signal recovers the attribution data that expires weeks before your customers are ready to buy — across every device and domain they touch.

Request a Demo View Platform