Cookie3 Docs
  • πŸ‘‹Introduction
  • πŸ‘‰Register your account
  • πŸ”ŒSetup your site or app
    • 1️⃣Add your website or app
    • 2️⃣Install Cookie3 snippet in your website or app
    • 3️⃣Installation guide
      • ⚑Integration with Google Tag Manager (GTM)
    • 4️⃣Verifying installation status
    • 5️⃣Security measures
    • 6️⃣Setup in-app custom events
    • 7️⃣Setting up consent management
    • How to retrieve your siteID?
    • ↗️Upgrading the snippet version
      • Troubleshooting
  • πŸ‘©β€πŸ’ΌAdd your team members
  • πŸͺFeatures
    • πŸ“ˆOnchain Explorer
      • Filters
      • Supported blockchains
      • Charts & metrics
      • Data export
      • CSV import
      • Audiences
    • πŸ•ΈοΈWeb Analytics
      • Selecting a website or app
      • Filters
      • Onchain reporting
      • Acquisition report
        • πŸ”ŽData dimensions
        • πŸ“ˆKey metrics
      • Conversions report
        • πŸ“ˆKey metrics
        • πŸ’²Show attribution report per conversion event
    • πŸ’²Conversion Events
      • How our attribution works?
      • Onchain conversion events
        • Attributed USD Value
      • Offchain conversion events
      • Retrieving your Conversion Event unique ID
    • 🐦KOL Intelligence
      • Getting started
        • Organic KOLs and Lists
        • KOL Dashboard
        • Searchbar
        • KOL Activity Chart
          • Extending the chart with additional Metrics
        • Advanced Metrics
        • Performance Table
          • KOL metrics explained
        • Post Feed
      • Your KOLs
        • Importing KOL Lists
          • Understanding the loading status during KOL upload
        • Managing KOLs in a given project
        • KOL List summary
      • AI-powered KOL scoring system
      • Campaigns
    • πŸ“ŠToken Analytics
  • βš™οΈAPI
    • πŸŒ€Referral Systems
      • Setup referral tracking
      • Accessing leaderboard and user data
      • API Response schema
      • Best practices
      • FAQ
Powered by GitBook
On this page
  • Understanding Conversion Events: OnChain and OffChain Goals
  • OffChain Conversion Events
  • OnChain Conversion Events

Was this helpful?

  1. Features

Conversion Events

PreviousShow attribution report per conversion eventNextHow our attribution works?

Last updated 3 months ago

Was this helpful?

In order to fully utilize this feature, please make sure you:

  • Have a site or app installed in Cookie3 Analytics.

Understanding Conversion Events: OnChain and OffChain Goals

Conversion events in our system are divided into two categories: OnChain Conversion Events and OffChain Conversion Events. These two types of goals reflect how we track and attribute key actions that users take, both on the blockchain and outside of it. While the general approach for tracking these events is similar, the attribution process varies depending on whether the goal occurs onchain or offchain.

You can learn more about Conversion Events and understand how our attribution model works .

OffChain Conversion Events

Offchain goals occur outside the blockchain, such as signing up for a newsletter, completing a purchase, or submitting a form. For these types of events, we are able to identify the specific visitor who fulfilled the goal based on traditional web tracking methods.

The key to offchain goal attribution is linking the event back to the exact visit that influenced the conversion. By identifying this visit, we can assign credit to the referrer or marketing source responsible for driving the user to complete the goal. Our attribution process ensures that the correct marketing touchpoints receive credit for the conversion.

OnChain Conversion Events

Onchain conversion events, such as completing a transaction or interacting with a smart contract, present a unique challenge because they occur directly on the blockchain. In these cases, we do not have direct information about the visitor who performed the onchain action, only the wallet address involved.

To solve this, we match the onchain action with the visitor by identifying website visits where the wallet in question was connected. Here’s how the process works:

  1. Search Website Visits: We go through all the website visits to find instances where the visitor connected the wallet that was used to complete the onchain goal.

  2. Select the Closest Visit: Once we have a list of visits where the wallet was connected, we select the visit closest to the goal completion date to maximize accuracy.

  3. Identify the Visitor: After selecting the visit, we match it to the visitor responsible for the action. While we cannot directly link the wallet action to a specific user, this method ensures we associate the goal with the most relevant visitor activity.

  4. Apply Attribution Model: After identifying the visit, we use the same attribution model as for offchain goals to credit the proper referrers and marketing sources.

Conclusion

By dividing conversion events into onchain and offchain categories, we ensure that every conversion, regardless of where it happens, is accurately tracked and attributed. While offchain goals allow us to directly identify the visitor, onchain goals require us to leverage wallet connection data to make the best possible attribution.

If you’re interested in learning more about how we attribute conversions, check out our detailed article on .

πŸͺ
πŸ’²
Read more
in this article
Attribution Models