Post view attribution helps advertisers recognize publisher influence beyond clicks. It allows Daisycon to attribute a conversion to a publisher when a user has seen a banner, even if the user did not click the ad before converting.
The feature is mainly intended for display, branding, and awareness campaigns where publisher value is created through visibility and reach.
What is post view attribution?
Post view attribution means that a conversion can be attributed to a publisher based on a banner view instead of a click.
For example: a user sees a banner on a publisher website, does not click it, but later visits the advertiser website directly and completes a conversion. If post view attribution is enabled and no valid Daisycon click is available, the conversion can be attributed to the publisher that generated the view.
Is post view attribution suitable for your campaign?
Post view attribution is most useful when publisher value is created through visibility and reach, rather than direct clicks alone.
Suitable use cases
- Display campaigns
- Branding and awareness campaigns
- Publisher collaborations focused on reach or exposure
- Campaigns with high visibility but relatively low click-through rates
Post view attribution may be less suitable when
- The advertiser only wants to reward conversions after a click
- Full view or impression reporting is required
- A separate base commission is required for view-based conversions
- The advertiser cannot support the required affiliate network deduplication setup
Important limitations and conditions
Before enabling post view attribution, keep the following points in mind:
- Post view attribution is attribution, not full view or impression tracking
- View and impression totals are not shown in MyDaisycon (statistics will be made available soon)
- The publisher must load banner material from Daisycon servers
- Clicks have priority over views within Daisycon
- The standard lookback window is 2 days, with a maximum of 5 days
- View-based conversions use the same base commission as click-based conversions
- The advertiser’s affiliate network deduplication setup must support view-based Daisycon activity
If Daisycon tracking only fires when a Daisycon click cookie, click ID, or network flag is present, post view attribution will not work reliably.
How views are registered
Daisycon post view attribution is cookieless. No post view cookie is set when the banner is viewed, and the publisher does not need to load a separate post view tracking script.
Instead, Daisycon registers the view through the banner material request. When the official banner code loads an image from Daisycon servers, the request can be registered as view data for attribution purposes.
The registered view can later be considered if the user converts within the configured lookback window.
Post view attribution is not full view tracking. Daisycon uses registered views for attribution, but does not provide complete view or impression statistics in MyDaisycon.
Banner implementation requirements
Post view attribution only works when the banner material request reaches Daisycon. The publisher must therefore use the official Daisycon banner code or another implementation that loads the banner material directly from Daisycon servers.
The publisher should not:
- Download and host the banner image manually
- Replace the Daisycon-hosted image URL with a self-hosted URL
- Prevent the banner material from loading when the page is viewed
If the banner image is hosted outside Daisycon, Daisycon cannot register the view.
Attribution priority and lookback window
Daisycon first checks whether a valid click is available. If there is a valid click, the conversion is attributed to that click. A registered view is only evaluated 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 lookback window determines how long a registered view can still be used for attribution.
Daisycon only applies this priority to clicks and views measured within Daisycon. Interactions from other affiliate networks must be handled through the advertiser’s own affiliate network deduplication setup.
Affiliate network deduplication
Post view attribution requires additional attention when the advertiser works with multiple competing affiliate networks.
A banner view does not automatically set an advertiser-side cookie, click ID, or network flag. A strict click-based cookie switch may therefore fail to recognize the earlier Daisycon view when the user later visits the advertiser website directly.
There are two common ways to support post view attribution:
- Broad catch-all setup: trigger the Daisycon conversion pixel when Daisycon is the known affiliate source, or when no competing affiliate network has been identified
- Last Event Counts: use the Daisycon LEC endpoint to make recent Daisycon event data available on the visitor’s client
Read more: Affiliate network deduplication and cookie switch setups.
Only deduplicate between competing affiliate networks
Affiliate network deduplication is intended to prevent duplicate commission payments between competing affiliate networks. It should not be used as a complete attribution model across all marketing channels.
We recommend against suppressing Daisycon tracking because SEA, paid social, display, email, direct traffic, or another non-affiliate channel was also involved.
Affiliate marketing is a post-paid channel, where commission is paid after a valid conversion. Many other channels are pre-paid or budget-based. Deduplicating a post-paid affiliate channel against a pre-paid channel can unfairly remove a valid affiliate commission, even though the advertiser has already paid for the other channel separately.
Cross-channel contribution can still be analyzed in the advertiser’s own attribution reports. This should remain separate from deduplication between competing affiliate networks.
Using Last Event Counts
Last Event Counts, or LEC, allows the advertiser to check whether recent Daisycon event data is available for the campaign and the visitor’s device or browser.
The advertiser can use the result to update its own cookie switch or deduplication marker. This is useful when the existing setup normally depends on click-based cookies, click IDs, or network flags.
A matching Daisycon view should not overwrite a newer known click from another competing affiliate network.
Any advertiser-side marker created from LEC data should use the same lifetime as the configured post view lookback window. It should not remain valid after the underlying view is no longer eligible for attribution.
Read more: Using Last Event Counts (LEC) for post view deduplication.
Example deduplication flow
A typical advertiser-side flow can look like this:
- A user sees a Daisycon banner on a publisher website
- The banner request reaches Daisycon and the view is registered
- The user later visits the advertiser website directly
- The advertiser checks for recent Daisycon event data through LEC
- The advertiser checks whether another competing affiliate network has already been identified
- If allowed by the agreed priority rules, Daisycon is stored as the affiliate network source for the configured post view window
- The user completes a conversion
- The advertiser’s cookie switch determines whether the Daisycon conversion pixel should fire
- Daisycon checks for a valid click first and only evaluates the view if no valid click is available
LEC supports deduplication and technical validation. It is not a view statistics or impression reporting endpoint.
Reporting
Post view attribution does not provide complete view or impression statistics. Registered views are used to determine whether a conversion can be attributed to a publisher.
Relevant view information can be added to the engagement data of an attributed transaction. This helps explain why the transaction was attributed, but it does not provide a complete report of all banner views.
- No separate view totals are shown in MyDaisycon
- No complete impression reporting is available
- LEC is not a reporting API
- Relevant view information can be available on transaction level
Commission setup
View-based conversions use the same base commission as click-based conversions. It is not currently possible to define a separate base commission based only on whether the conversion followed a click or a view.
Existing custom commissions can still apply for:
- Specific publishers
- Specific media
- Specific media types
Conclusion
Post view attribution allows advertisers to recognize publisher influence from banner visibility, not only from clicks. It is mainly suitable for display, branding, and awareness campaigns. Reliable attribution depends on Daisycon-hosted banner material, click priority, an agreed lookback window, and a suitable affiliate network deduplication setup. The feature should be positioned as view-based attribution, not as full impression tracking or reporting.