To gain access to this feature, reach out to the customer success team via support@everflow.io.


Overview

The User Management feature allows you to track an individual User across multiple Offers and Partners, and apply changes to the Revenue & Payout settings associated with that User's conversions. These changes can be based on various Data Points passed into Everflow when a conversion happens.

Use Case Examples:

  • If you operate websites that sell different types of insurance (auto, homeowners, travel), you can use a user's phone number to track their activity across all of your websites. If a user indicated interest in auto or homeowners insurance, and ends up purchasing travel insurance, you may want to pay the Partner more than you would if the user hadn't shown interest in your other offerings.

  • If you sell different varieties of pancakes, you can use a customer's email address to track each purchase. You may want to pay the Partner more per sale once that customer purchases your product 5 times.

Please note that to use this feature, the advertiser (i.e. brand) must be able to pass back a unique User ID. This could be an email address, phone number, or any other random string.


A How-To Guide with Example

The example shown here uses the user’s email address as the User ID and illustrates how to increase the Partner’s payout to $10 per conversion for a user who has made at least 4 purchases of blueberry pancakes in the same month.

Step #1: Data Points

Data Points pass values that are associated with Users. A Data Point is passed using a custom parameter you define. You may add as many Data Points as you wish.

In the example below, the Data Points correspond with different ways to count pancake purchases.

  1. Navigate to User Management - Data Points. Click + Add, or click the vertical dots to edit an existing entry.

  2. Set the Name and Status, and define the Parameter that will be used to pass the Data Point into Everflow.

    **Please note that the Parameter will be added to the Postback URL/Pixel/Conversion Script and therefore must be formatted without spaces and in lowercase letters. Underscore [ _ ] is the only special character allowed.

To skip forward to instructions for adding your Data Points to the Conversion Method - [Click Here]

Step #2: Rules

Rules define the circumstance in which a Revenue/Payout configuration will be applied.

  1. Navigate to User Management - Rules. Click + Add.

  2. Set the Name, Status, Start and End Dates (optional), and pay close attention to the following:

    • Targeted Entity Type: Tie the configuration to specific Offers or specific Advertisers.

    • Available Advertisers/Offers/Partners: Choose specific selections or “Select All”. Note the funnel icon in the search bar for further filtering abilities.

    • Aggregation Level: Select the level at which a rule should be aggregated. For example, selecting User + Partner means the configuration will apply to each unique User ID/Partner ID combination.

  3. Click Save.

Step #3: Rule Settings

Click the Settings tab.

Define the settings that will apply to the rule and Save. See below for information about each field.

Time Period

The specific time period to which the rule applies. Time Periods will be reset at the following times:

  • Daily: 00:00:00*

  • Weekly: Monday at 00:00:00*

  • Monthly: The 1st at 00:00:00*

  • Global: Infinite

* Based on the timezone configured in Control Center - Configuration or the specific timezone associated with Offer Caps (if applicable).

Event

Tie the rule to a specific event or all events and associated Goals. If you've selected more than one Offer on the previous page (General), you will only be able to select All Events.

Goals

Please note that if you add more than one Goal, conditions for ALL goals must be met before the Rule is applied.

  • Metric: Choose the metric that initiates the Rule (i.e. Conversion refers to the number of base conversions).

  • Data Point Parameter: Only visible if Data Point is selected as the Metric.

  • Aggregation Type / Operator / Value: Choose how to calculate the relevant data before applying the Rule.

**PLEASE READ CAREFULLY**

The feature does not process data in "real time", and therefore the existing data must be "true" to the configured Rule Settings BEFORE the Rule can be applied.

  • In the Pancakes Rule example, we want to apply a different Partner Payout at the time of a customer's 5th purchase in the same month, so the Operator is Greater Than, and the Value is 3.

    Why? After the 3rd conversion, the 4th conversion will be fired with the original payout. At this point, the number of existing conversions (4) is officially greater than 3, so the data assessed by the feature is "true" according to the Rule Settings.

  • If we wanted to apply a different Partner Payout for ONLY the 5th conversion but not all the subsequent conversions, the Operator would be Equal and the Value would be 4.

    Why? The number of existing conversions must be "true" before the feature can apply the Rule. Once there are 4 conversions, the existing data becomes "true" according to Rule Settings. Once a 5th conversion happens, the existing data is no longer "true" according to the Rule Settings, and therefore the Rule cannot be applied anymore.

Revenue & Payout

  • Enable Payout/Revenue: Increase or decrease the Payout/Revenue either by a Percentage of the original payout, by a Flat Amount based on the original payout, or use a fixed amount to override the original payout/revenue altogether by selecting Exact.

In summary, using the same Pancakes Rule example, if a Partner/User combo generates 4 conversions with the Data Point: blueberry_pc=1 in the same month, then each subsequent conversion driven by that Partner, from that User, during the same month, will have a $10 Payout. When the next month begins, the cycle resets and starts counting from zero.

Step #4: Conversion Methods

Each Offer is set up with a specific Conversion Method, meaning that each Offer depends on either a Server Postback, HTML Pixel, or Conversion Script to receive conversion data.

It is your responsibility to adapt your Postback URL(s), Pixel(s), and/or Conversion Script(s) to be able to receive the user_id and other relevant Data Points.

In the examples below, the unique User ID will be the user’s email address, and the Data Point for Blueberry Pancakes will be appended with its defined parameter: blueberry_pc

Server Postback

https://www.yourdomain.com/?nid=XXX&transaction_id=TRANSACTION_ID&user_id=ilovepancakes@gmail.com&blueberry_pc=1

HTML Pixel

<img src="https://yourdomain.com/?nid=XXX&oid=xxx&user_id=ilovepancakes@gmail.com&blueberry_pc=1" width="1px" height="1px" />

JS SDK Conversion Script

EF.conversion({
aid: 1,
user_id: 'ilovepancakes@gmail.com',
parameters: {
'blueberry_pc': '1',
}
});

For a detailed guide on setting up Conversion Methods - [Click Here]

(Optional) Step #4: Conversions

Navigate to User Management - Conversions. You can search for conversion details per User ID.

(Optional) Step #5: Reporting

Navigate to Analytics - Flex.

You can add columns for desired Data Points.

Or, click UM Metrics to use Data Points as metrics for the report.


NEED HELP? OUR CUSTOMER SUCCESS TEAM IS HERE FOR YOU!

We've assembled a superstar team of industry veterans that are available around the clock to make sure that your issues are resolved and questions are answered. You can reach out any time in-platform via Chat or by emailing support@everflow.io.

Did this answer your question?