Conversion events

Conversion events collect user revenue in one uniform format so you can use it for attribution, analytics, and segmentation.

What are conversion events

Pushwoosh records revenue from user transactions as PW_Conversion, a built-in event. Each record includes:

• value: the transaction amount
• currency: ISO 4217 currency code
• transaction_id and product_id: optional identifiers

PW_Conversion covers purchases, subscription renewals, and payments from third-party platforms, regardless of where the original money event comes from.

Alongside default and custom events, conversion events are a third event category in Pushwoosh. Pushwoosh normalizes revenue from differently shaped source events (such as OrderPlaced, CheckoutSuccess, PW_InAppPurchase, or Stripe and Shopify webhook events) into PW_Conversion records.

Revenue reaches Pushwoosh in one of two ways:

• Send PW_Conversion from your code: your app or backend sends the event directly after a purchase.
• Map an existing event in the Control Panel: map a purchase event you already send to PW_Conversion without changing your code. You can map more than one source event per application.

Whichever path you use, Pushwoosh stores one normalized record per conversion. Segmentation, Customer Journeys, dashboards, and ManyMoney AI all read from the same data.

Important

Use only one path per transaction. If you send PW_Conversion directly and also map another event that fires for the same purchase, Pushwoosh records both as separate, independent PW_Conversion events. Pushwoosh does not detect or merge duplicates across sources, even when they share a transaction_id.

Use cases

Once conversion events are set up, that data becomes usable everywhere revenue matters in Pushwoosh:

• Build RFM segments for high-value users based on spend amount and recency, without custom revenue logic for each event.
• Attribute revenue to Customer Journeys and campaigns. See which flows drive purchases, not just clicks or opens.
• View revenue in dashboards and reporting without building custom logic for each purchase event.
• Combine revenue from SDK purchase events and payment webhooks (Stripe, Shopify) into one dataset instead of analyzing each source separately.
• Let ManyMoney AI use real transaction data in its recommendations and campaign optimizations.

How to set up conversion events

Conversion events are configured per application. You can set up conversion events in one of two ways. Follow the instructions for the path that fits your implementation.

Send PW_Conversion from your code

This path fits when you can add or change event code in your app or backend. After each purchase, send PW_Conversion through the postEvent method.

Developer assistance needed

To send PW_Conversion from your code, you’ll need help from your development team. Share the sample from View code, along with this link with them for instructions.

1. Go to Audience > Events. Find the Conversion events tracking card.

2. Click View code.

3. Copy the sample and add the postEvent call wherever a purchase completes in your app or backend.

提示

Only value and currency are required. transaction_id and product_id are optional.

If you send transaction_id, Pushwoosh stores it exactly as you pass it. It does not deduplicate revenue by this field.

Example for JavaScript:

Pushwoosh.postEvent("PW_Conversion", {
    value: 49.99,
    currency: "USD",
    transaction_id: "ord_18274",
    product_id: "sku_premium_m"
});

Attributes for the postEvent call

The following table lists the attributes you can pass when sending PW_Conversion.

Field	Type	Required	Description
value	number	Yes	The monetary amount of the transaction.
currency	string (ISO 4217)	Yes	The transaction currency code, for example USD or EUR.
transaction_id	string	No	A unique identifier for the transaction. Recommended for your own record-keeping. Pushwoosh stores it as-is but does not use it to deduplicate revenue on its own.
product_id	string	No	The identifier of the purchased product or plan.

警告

Conversion events do not currently support refunds or cancellations. There is no way to send a negative or reversing PW_Conversion record. Once a transaction is recorded, it stays in your revenue totals even if the purchase is later refunded or canceled.

Map an existing event to track revenue

This path fits when purchase data already flows through another event and you do not want to change your code. When a mapped source event arrives, Pushwoosh fires and records it as a PW_Conversion event.

注意

Mapping does not change or replace the source event. It keeps working exactly as before. The source event stays available in segmentation, event history, and dashboards like any other event. Pushwoosh additionally creates a PW_Conversion record from it, used only for revenue features.

1. Go to Audience > Events. Find the Conversion events tracking card.

2. Click Start collecting revenue (or Event mapping, if you’ve already mapped an event). The Set conversion events page opens.

3. In Use existing events to track conversion, open the EVENT dropdown and select the event you already send. The list includes custom events, default events, and inbound-webhook events (such as Stripe or Shopify).

4. Map the remaining attributes:

   • In PRICE, select the attribute that stores the transaction amount.
   • In CURRENCY, select the attribute that stores the currency code.
   • Optionally, map TRANSACTION ID (OPTIONAL) and PRODUCT ID (OPTIONAL).

To map another source event, click + ADD EVENT. To remove a mapping, click REMOVE.

5. Click Apply.

You can map multiple events as sources for the same application. For example, map a custom purchase_completed event alongside a Stripe webhook event.

Important

Changes won’t recalculate past statistics. Only new conversion data will use the updated setup.

How does Pushwoosh handle multiple currencies

Pushwoosh stores and sums revenue separately for each transaction currency. It does not convert everything into a single base currency yet. If your app charges in multiple currencies, expect totals broken out by currency rather than one combined number.

Monitor conversion events

The Conversion events tracking card on Audience > Events summarizes conversion activity for the selected application. It shows two numbers:

• Mapped events: how many source events currently feed into PW_Conversion.
• Triggered last 7 days: the total number of PW_Conversion events fired in that window, from any current or past mapping, or from direct postEvent calls.

Click View code to reopen the PW_Conversion integration sample.

Important

This count reflects every PW_Conversion event fired in the last 7 days, regardless of source. If you change or remove a mapping, past PW_Conversion events it already generated stay counted until they age out of the 7-day window. The number doesn’t drop or recalculate right away.