Ad attribution and conversion feedback

Know which ads create qualified pipeline—not just clicks and form fills.

Sissel connects consented website journeys to CRM stages and revenue. Inspect the evidence behind every attribution, then send the qualified outcomes you choose back to Meta and Google.

Create beta accountSee how it works
Consent-aware collectionNo conversion delivery until you enable itBuilt in Norway
Redacted product example · Inspectable outcome evidence

Qualified outcome — p•••@example.no

A chronological explanation, not a black-box score. Representative data; no customer claim.

Example data
  1. Touchpoint

    Meta ad visit

    /book-demo

    Campaign
    summer-pipeline

    Campaign and ad IDs observed on the landing URL.

  2. Identity

    Signed form-token evidence

    The consented form carried the signed browser-to-server token.

  3. Stage change

    Outcome received: qualified lead

    Qualified lead

    Received from CRM and linked to the same person record.

  4. Delivery

    Meta conversion delivery

    Succeeded · Test

    Selected mapping in Test mode; no production optimization.

Why Meta received credit

Last non-direct · 30-day lookback · model v1

Credited

The Meta visit was the latest eligible non-direct touchpoint before the qualified outcome.

Excluded

A later direct visit carried no campaign source, so this named model did not replace the paid touchpoint.

Exact scope

Workspace
Nordic demand
Site
example.no
Window
8–11 July 2026 UTC+2
Outcome
CRM qualified lead
How it works

From ad click to recorded outcome.

Each step stays visible so your team can check the result instead of accepting a black-box number.

01

Record a consented visit

Sissel records the campaign details that arrived with the visit. In strict mode, nothing is collected before consent.

02

Link it to an outcome

A tracking token or exact identifier connects the visit with a lead, deal or sale from your business systems.

03

Credit the campaign

Choose a clear attribution model. Sissel stores the model, window and evidence used for each result.

04

Send only what you choose

Test selected outcomes with Meta or Google before enabling live delivery. Every attempt remains visible.

Attribution is not causality

Sissel shows which sources preceded and were credited for an outcome. It does not claim that an ad caused the sale.
Why teams use it

Every attributed outcome comes with evidence.

Explainable journeys

Open a result and see the visits, identity evidence, attribution decision and delivery history behind it.

Clear collection limits

No browser fingerprinting, anonymous contact enrichment or identity sharing between customers.

Recoverable delivery

Failed conversion deliveries can be retried without quietly sending the same outcome twice.

Problems named plainly

See whether tracking is waiting for setup, missing data, delayed or genuinely failing—and what to do next.

Beta evidence register

We distinguish demonstrated product behaviour from customer evidence that has not been supplied or approved for publication.

DemonstratedRedacted evidence journey

The product example above mirrors the implemented journey ledger: touchpoints, explicit identity evidence, named attribution model/version, exclusions, outcomes, and conversion deliveries.

Not yet publishedCustomer and founder proof

No design-partner names, customer quotes, production performance metrics, or founder biography are claimed on this site until they can be verified and approved. We will not use placeholder logos or invented results.

Connections

Connect the systems involved in the sale.

Bring in outcomes through a supported CRM connector, Zapier or the public API. Add ad data separately, then choose which results are sent back.

View compatibility

Sources

CRM outcomes, form systems, server events and Zapier

Advertising data

Meta and Google campaign structure and spend

Destinations

Selected outcomes as conversion deliveries, tested before Live

Privacy and control

Responsible measurement, with clear limits.

Sissel records the consent state with each event. In strict mode, missing consent means the event is not collected. Connecting a destination never enables sending by itself.

Consent-awareNo fingerprintingNo cross-customer identity
Read how data is handled

Deliberate non-goals

What Sissel does not try to infer or automate.

  • Browser or device fingerprinting
  • Anonymous visitor contact enrichment
  • Identity sharing between customers
  • Opaque multi-touch credit allocation
  • Sending every observed event without review

Install alongside your current setup.

Compare results in test mode before enabling a production conversion destination. Your existing Meta Pixel and Google tag can keep running.

Create beta account