Post view attribution for publishers

With post view attribution, you may receive commission when a visitor sees your banner and later converts, even if the visitor did not click the ad. This can help recognize the value of display and branding placements where visibility is important.

What is post view attribution?

Post view attribution means that a conversion can be assigned to you based on a banner view instead of a click.

For example: a visitor sees your banner, does not click it, and later visits the advertiser’s website directly to complete a conversion. If post view attribution is enabled and no valid Daisycon click is available, the conversion may be attributed to your view.

When can post view attribution benefit you?

Post view attribution is most relevant when your media value comes from visibility and reach rather than direct clicks alone.

• You use display or banner placements
• Your media focuses on visibility, awareness, inspiration, or reach
• Your placements generate exposure but relatively few direct clicks
• The advertiser has enabled post view attribution for the campaign

Important points to know

• The solution is cookieless
• No separate post view tracking script is required
• The banner material request is used to register the view
• The banner must be loaded from Daisycon servers
• Clicks have priority over views within Daisycon
• The standard lookback window is 2 days, with a maximum of 5 days
• Views are used for attribution, not full impression reporting
• View-based conversions follow the advertiser’s existing commission setup

If you download a banner image and host it yourself, Daisycon cannot register the view.

How are views registered?

Daisycon post view attribution is cookieless. No post view cookie is set when a visitor sees the banner, and no additional post view tracking script is required.

Instead, the banner material request is used to register the view. When the banner is loaded from Daisycon servers, Daisycon can register the request as view data for attribution purposes.

If no cookie or additional tracking script is visible, this does not mean that post view attribution is inactive.

Banner implementation requirements

Post view attribution only works when the banner request reaches Daisycon. You must therefore use the official Daisycon banner code or another implementation that loads the banner material directly from Daisycon servers.

Make sure that you:

• Keep the Daisycon-hosted banner image URL in the banner code
• Use the correct media ID in the banner request
• Allow the banner material to load when the placement is shown

Do not download the banner image, upload it to your own server, or replace the Daisycon-hosted image URL with another URL.

The banner material request and the click URL have different purposes. The banner request allows the view to be registered. The click URL registers a click when the visitor selects the banner.

How does attribution work?

Within Daisycon, clicks have priority over views. If a visitor sees your banner but later clicks another valid Daisycon affiliate link before converting, the conversion is attributed to the click.

• A valid Daisycon click has priority over an earlier view
• A view is only considered when no valid Daisycon click is available
• The standard post view lookback window is 2 days
• The maximum supported lookback window is 5 days

The actual lookback window depends on the advertiser’s campaign settings. Daisycon applies this priority to clicks and views measured within Daisycon.

How to test post view attribution with LEC

You can use the Last Event Counts endpoint to verify whether a banner view has been registered for the selected campaign and your current device or browser.

The endpoint has the following structure:

https://<tracking_domain>/js/lec/?ci=<program_id>

• <tracking_domain> is the Daisycon tracking domain used for the campaign
• <program_id> is the Daisycon campaign ID

Step 1: Check the endpoint before loading the banner

Open the LEC endpoint in the browser and device you will use for the test.

If you have not recently viewed a banner from the campaign, the response should indicate that no matching event was found:

Step 2: Load the Daisycon-hosted banner

Load the banner on an external test page using the official Daisycon banner code. This tests the same implementation that will be used on your website.

You can also load the Daisycon-hosted banner image URL directly in the same browser for a basic registration test.

Do not perform the test by browsing banner material inside MyDaisycon. Views inside Daisycon interfaces are excluded and will not be registered.

Step 3: Refresh the LEC endpoint

Return to the LEC endpoint and refresh the page. If the banner view was registered, the response should indicate that a matching event was found.

The following example uses fictional values:

Step 4: Validate the result

Check the following values:

• status should be G
• iso_date should match the time of your test
• media_id should match the media used in the banner request

If no matching view is found

Check whether:

• The banner was loaded from Daisycon servers
• The official banner image URL was kept unchanged
• The correct campaign ID was used in the LEC endpoint
• The correct tracking domain was used
• The banner and LEC endpoint were loaded in the same browser and on the same device
• The test was performed outside MyDaisycon or another Daisycon interface
• The banner request was not blocked by a browser extension, privacy tool, or network setting

LEC is intended for deduplication and technical verification. It does not provide complete view statistics or campaign-wide impression reporting.

What reporting is available?

Post view attribution is not the same as full view tracking or impression reporting. Registered views are used to determine whether a later conversion can be attributed to a publisher.

• No separate view or impression totals are shown in MyDaisycon
• LEC only checks recent event data for the selected campaign and local device or browser
• LEC does not provide campaign-wide view statistics
• Relevant view information can be added as engagement data on transaction level

Commission and payouts

View-based conversions use the same base commission as click-based conversions. There is currently no separate base commission based only on whether the conversion followed a click or a view.

Existing custom commission settings can still apply to:

• Specific publishers
• Specific media
• Specific media types

The advertiser remains responsible for enabling post view attribution and configuring the campaign’s commission settings.

Conclusion

Post view attribution can help you receive credit for visibility, not only clicks. The solution is cookieless and uses the Daisycon-hosted banner request to register the view. Correct banner implementation is therefore essential. You can use LEC to verify that a view was registered, but it does not provide full view or impression reporting.