Skip to main content
All CollectionsData ConnectorsCustom Connectors
How to request Everflow data in Funnel
How to request Everflow data in Funnel

Leverage your Everflow data in Funnel via Custom Connectors.

Kelsey Maynard avatar
Written by Kelsey Maynard
Updated this week

If your use case requires this data in Funnel, you can request it as a Custom Connector.

Custom Connectors and the Custom Connector Request feature are available in the following plans: Business and Enterprise. See our Pricing page for more details.


General Fields

  • Date: The specific day when an event (such as a click, conversion, or impression) occurred.

  • Currency (always "USD"): The monetary unit used for all financial metrics, set to U.S. Dollars (USD) in this context.

  • Network Advertiser ID: A unique identifier assigned to each advertiser within the Everflow network.

  • Advertiser Name: The name of the company or entity offering the product or service being promoted.

  • Impressions: The number of times an advertisement is displayed to users.

  • Gross Clicks: The total number of clicks recorded, including unique, duplicate, and invalid clicks.

  • Total Clicks: All valid clicks, encompassing both unique and duplicate clicks.

  • Duplicate Clicks: Clicks from users who have clicked on the same offer multiple times within a defined session period.

  • Invalid Clicks: Clicks that are disqualified due to reasons such as targeting mismatches, capping violations, traffic filtering, or proxy usage. These clicks do not reach the destination URL but are redirected to fail traffic offers or a blank page.

  • Total Conversions: The sum of base conversions and view-through conversions.

  • CV (Conversions): The total number of base conversions, representing successful actions completed by users, such as purchases or sign-ups.

  • Invalid Conversions Scrub: Conversions that have been invalidated or removed, often due to fraud detection or failure to meet specific criteria.

  • View Through Conversions: Conversions attributed to users who viewed an advertisement but did not click on it before converting.

  • Events: Additional tracked actions that occur after the initial conversion, such as account registrations or in-app purchases.

  • View Through Events: Events attributed to users who viewed an advertisement without clicking on it before performing the event action.

  • Profit: The difference between revenue earned from advertisers and the payout made to partners, calculated as Revenue minus Payout.

  • Average Sale Value: The average monetary amount per sale, calculated by dividing Gross Sales by Total Conversions.

  • Payout: The amount paid to partners or affiliates for driving conversions or traffic.

  • Revenue: The total amount earned from advertisers for the traffic or conversions delivered.

  • Margin: The profit expressed as a percentage of revenue, calculated as (Profit / Revenue) * 100.

  • Gross Sales: The total sales amount, representing the sum of all sale values recorded.

  • Gross Sales VT: The total sales amount attributed to view-through conversions.

  • Media Buying Cost: Expenses incurred from purchasing media placements to drive traffic or conversions.

  • Unique Clicks: Approved clicks from distinct users. If the same user clicks on the same offer again within the session duration, it is not counted as a unique click.

Raw Conversions Report Fields

  • Conversion ID: A unique identifier assigned to each recorded conversion.

  • Date (converted from unix timestamp): The date and time when the conversion occurred, derived from a Unix timestamp.

  • Sub1, Sub2, Sub3, Sub4, Sub5: Customizable sub-affiliate parameters used to pass additional information or track specific data points related to the conversion.

  • Source ID: An identifier representing the traffic source or partner responsible for the conversion.

  • Revenue Type: The model used for calculating revenue, such as CPA (Cost Per Action) or CPC (Cost Per Click).

  • Session User IP: The IP address of the user at the time they clicked on the tracking link.

  • Conversion User IP: The IP address of the user at the time the conversion was recorded.

  • Country, Region, City: Geographical information indicating where the user was located during the session or conversion.

  • Carrier: The internet service provider or mobile carrier used by the user.

  • Platform: The operating system or environment on which the user's device is running (e.g., iOS, Android).

  • OS Version: The specific version of the operating system on the user's device.

  • Device Type: The category of device used by the user, such as mobile, desktop, or tablet.

  • Brand: The manufacturer of the user's device (e.g., Apple, Samsung).

  • Browser: The web browser used by the user during the session.

  • Language: The language setting of the user's device or browser.

  • HTTP User Agent: A string that identifies the user's browser, device, and operating system to the server.

  • Is Event: A boolean value indicating whether the recorded action is an event beyond the base conversion.

  • Event: The specific name or type of event recorded, such as "Registration" or "Purchase."

  • Transaction ID: A unique identifier associated with the user's click session, used to match clicks to conversions.

  • Click Unix Timestamp: The exact time when the user clicked on the tracking link, represented as a Unix timestamp.

  • ISP: The Internet Service Provider used by the user during the session.

  • Referer: The URL of the webpage that directed the user to the tracking link before the click or conversion occurred. It helps identify the source of traffic by showing which site or platform the user came from before interacting with the offer. This field is useful for tracking referral sources, analyzing user journeys, and optimizing marketing campaigns.


How to Request this Custom Connector

To request Everflow data, submit a Custom Connector Request (see link here for instructions).

If you are interested in Everflow data that hasn't been covered here, we would like to encourage you to connect with our Integration Engineering team by submitting a Custom Connector Request. They will be more than happy to explore the potential of obtaining additional data.

Did this answer your question?