The background on PixelRelay's Recharge connection. To set it up, see Connect Recharge.
Recharge sends PixelRelay a webhook for each subscription change. PixelRelay sends the purchases to your ad platforms and the whole subscription story to Klaviyo and Segment. It checks every webhook against your Webhook signing secret, so it only acts on ones that really came from Recharge. The secret is stored encrypted.
What gets sent
| Recharge webhook | Where it goes |
|---|---|
order/created, first order | Ad platforms as a purchase, GA4, Klaviyo, Segment |
order/created, renewal | The ad platforms you ticked, GA4, Klaviyo, Segment |
subscription/… (created, activated, updated, skipped, unskipped, paused, cancelled) | Klaviyo and Segment only |
charge/upcoming, charge/failed, charge/max_retries_reached | Klaviyo and Segment only, e.g. Upcoming Subscription Charge and Failed Subscription Payment for reminder and failed-payment flows |
charge/refunded | Not sent. Shopify's own refund already covers it |
Renewals
New subscription orders always go to your connected ad platforms. For renewals, you choose per platform under Renewal destinations. Only connected platforms show up.
| Platform | Renewals by default | Sent as |
|---|---|---|
| Meta, TikTok, Snapchat, Reddit | On | Purchase |
| On | Checkout | |
| Google Ads | Off | Your Purchase action, or a separate renewal action |
| Microsoft Ads | Off | A purchase, or subscription_renewal if you use a separate renewal goal |
| Google Analytics 4 | Always sent | purchase |
| Klaviyo, Segment | Always sent | Subscription events |
Google Ads and Microsoft Ads start off because a renewal usually has no new ad click behind it. If you turn Google Ads on, add a Google Ads renewal conversion action (optional) so renewals don't mix with first purchases. Without one, renewals use your normal Purchase action and can affect bidding.
Duplicates
A Recharge order is usually a Shopify order too. PixelRelay matches the two by the Shopify order ID, so it doesn't send that order twice.
Troubleshooting
| What you see | What to do |
|---|---|
| Upgrade required on the Recharge card | Recharge needs Growth or higher. Change plan in Plan & Billing. |
| Nothing arrives from Recharge | The webhooks probably don't exist yet, or point at a different URL. Ask whoever created them to check each topic uses the Webhook URL from PixelRelay. |
| Webhooks arrive but get rejected | The secret doesn't match. It must be the API Client Secret of the same token that created the webhooks. |
| Renewals missing on one ad platform | That platform is unticked under Renewal destinations. Google Ads and Microsoft Ads start off. |
| Recharge events stopped after a plan change | On Launch, PixelRelay skips Recharge events. |
Disconnect
Connections → Recharge Subscriptions → Disconnect, then confirm. PixelRelay stops using Recharge events. Ask your developer or Recharge support to delete the webhooks too, so Recharge stops sending them.
Related
Need help? Email [email protected]