Overview
In Funnel we will give you a default option that we recommend for you from the fields that you have selected when creating or editing a Conversion Upload. But if you want to understand this option or want to tweak it then this article is for you.
How to think of this option is: If a certain field value changes do you want to upload the row again as a new conversion. If you want to send returns then you want to include the conversion value field as a trigger so that when the value changes to a negative number it will be uploaded as a new conversion (this use case is not supported by Facebook). And maybe the user phone number changes in your CRM and you want to upload it if you have it but not upload it again as a new conversion just because it changes then you make sure to unselect it as an Upload trigger.
Note that even if you have selected a lot of Upload triggers they might not be counted in the destination platform depending on your selection when setting up the conversion action/rule. If you have selected "Count one" when configuring the Conversion Action in Google Ads for example then they will only count one conversion per user.
How you configure your upload triggers might also depend on the destination platform. Facebook mostly uses the User attributes for matching target customers and you therefore will want to send as up-to-date values for them as possible while product attributes matter less. While for Google Ads you might want as accurate sales data as possible to not spend money on targeting low value customers.
Example 1
Rows in Funnel
Conversion time | Order ID | |
2025-01-01 | 001 | |
2025-01-01 | 002 | |
2025-01-02 | 003 |
Uploaded rows case 1
If you have "Conversion time" and "Email" selected as Upload triggers.
Conversion time | Order ID | |
2025-01-01 | 001 | |
2025-01-02 | 003 |
Uploaded rows case 2
If you have "Conversion time", "Email" and "Order ID" selected as Upload triggers.
Conversion time | Order ID | |
2025-01-01 | 001 | |
2025-01-01 | 002 | |
2025-01-02 | 003 |
Example 2
Rows in Funnel
Where the first row gets a phone number populated many hours or days later, visualised as the second row.
Conversion time | Phone number | |
2025-01-01 | <empty> | |
2025-01-01 | +1 123 456 | |
2025-01-02 | +1 123 456 |
Uploaded rows case 1
If you have "Conversion time" and "Email" selected as Upload triggers.
Conversion time | Phone number | |
2025-01-01 | <empty> | |
2025-01-02 | +1 123 456 |
Uploaded rows case 2
If you have "Conversion time", "Email" and Phone number selected as Upload triggers.
Conversion time | Phone number | |
2025-01-01 | <empty> | |
2025-01-01 | +1 123 456 | |
2025-01-02 | +1 123 456 |
Example 3
Rows in Funnel
When a return comes in many hours or a few days later visualised as the second row here but the conversion time is the same.
Conversion time | Quantity | Conversion value | |
2025-01-01 | 1 | 100 | |
2025-01-01 | -1 | -100 | |
2025-01-02 | 1 | 100 |
Uploaded rows case 1
If you have "Conversion time" and "Email" selected as Upload triggers.
Conversion time | Quantity | Conversion value | |
2025-01-01 | 1 | 100 | |
2025-01-02 | 1 | 100 |
Uploaded rows case 2
If you have "Conversion time", "Email" and Quantity or Conversion value selected as Upload triggers.
Conversion time | Quantity | Conversion value | |
2025-01-01 | 1 | 100 | |
2025-01-01 | -1 | -100 | |
2025-01-02 | 1 | 100 |