Skip to main content
By default, destinations receive the value already on the event. You can override it so your ad platforms optimize on something else — profit instead of revenue, or a flat value for leads. Set it while creating a mapping — global or destination — by turning on Override event value and picking under Set value to.

What you can send

What’s available depends on the base event: Net Revenue comes straight off the Shopify order. CM1 and CM2 subtract your cost settings from it, which needs the full order — so they’re purchase-only:
  • CM1 = Net Revenue − product cost
  • CM2 = CM1 − shipping, handling, and payment fees
If you pick an option the event can’t supply, Upstack sends the event’s own value rather than a wrong number.

Custom formula

Two ways to build one:
  • Simple — pick a value and adjust it step by step, like a calculator: Event value × 0.7. Each part is a metric, a field (data.fieldName), or a number.
  • Advanced — type the formula directly, with autocomplete. Use + − * / and parentheses.
A missing field never zeroes your value. If a formula references a field the event didn’t send, Upstack skips the override and forwards the event’s own value. A field that is present and genuinely 0 is used as 0.

Operands

From the event — any event: Revenuepurchase, add_to_cart, initiate_checkout, view_content: Costspurchase only, from your cost settings:

Global event mappings

Create a mapping once and send it everywhere.

Cost settings

Configure the costs behind Net Revenue, CM1, and CM2.

Custom events overview

What custom events are and when to use them.

Destination event mappings

Set a different value for one destination.