Oriva

Migrating from Stape to Oriva

Published on by the Oriva team.

You do not have to cut Stape to try Oriva. The order that avoids losing a sale or counting it twice: export your configuration, plug Oriva in beside it without making it send anything, check that collection arrives, then switch one platform at a time (cut the send at Stape and turn on the destination at Oriva the same day), and only then cancel. According to Stape, a cancelled subscription keeps running until the end of the paid cycle. The one real risk is that a sale goes out twice to the same platform during the overlap. Stape publishes no guide to leaving it: what this page says about Stape comes from pages we read on October 13, 2026, and what they do not say is flagged as such.

A sale while moving from Stape to Oriva: with a single active path per platform it is counted once; with both active it is counted twice.

What actually migrates?

Stape sells two separate products, and the migration differs for each.

A server GTM container hosted at Stape. Your configuration lives in Google Tag Manager: that is where the container is exported (Admin, Export Container, a .json file), not at Stape. Oriva does not read a GTM container: each destination is recreated through a form (Meta, TikTok, Google Ads, ChatGPT Ads, postback). What is not an ad conversion (an analytics tag, a third-party script) has no equivalent at Oriva: see “Who doesn't need to migrate?”.

The Meta Conversions API Gateway. It copies the events of your Meta pixel. Your pixel is code on your site: leaving the gateway does not remove it. But Stape asks that the gateway's subdomain match the one the pixel uses: before you delete it, check that your pixel no longer depends on it. Stape does not document this case.

In what order?

  1. Keep your configuration. Export your container from Google Tag Manager before touching anything. Stape describes this export on its migration page, which explains the way in to Stape: the gesture is the same the other way. A copy of the list of your tags and triggers will help you recreate each destination.
  2. Plug Oriva in beside it, without turning it on. Create the domain, add the tracking code, create one destination per platform, then turn it off right away: a destination is active as soon as it is created. Turned off, it sends nothing, and Oriva keeps receiving and recording your events. The “Test this destination” button checks your token and your account with a made-up event that is tied to none of your sales.
  3. Look at what arrives. The Events tab shows what Oriva receives: how many events of each type, what share carries advertising consent, and the last one received. Compare with what Stape or your pixel report for the same days.
  4. Give both sides the same identifier. With the gateway, Stape says it generates the deduplication identifier itself and propagates it to both sides. Once the gateway is gone, nothing guarantees your pixel still carries one: give it your order reference as the event identifier, and give it to Oriva as event_id. That is the rule of the double counting guide.
  5. Switch one platform at a time, on the same day. Cut the send at Stape (turn off the gateway or the matching tag), then turn on the destination at Oriva. Never let two server paths send the same sale to the same platform at the same time: that is the only case where you count twice.
  6. Check at the platform. In Meta Events Manager or the equivalent tool, look that a single purchase arrives per order, with its identifier. Once the destination is on, the Health tab flags two useful cases: the same order reference seen on the browser side and the server side, and a platform pixel detected while an Oriva destination exists for it (a warning: it asks you to check that both send the same identifier, it does not say that something is broken).
  7. Cancel Stape. Only when steps 5 and 6 are good.

How do you cancel at Stape?

In Stape's dashboard: open the container or the gateway, click the three dots at the top right, “Cancel Subscription”, pick a reason, then finish with the confirmation email (Stape page updated August 3, 2026). A subscription covers one container: if you have several, cancel them one by one.

According to the same page, the product keeps running until the end of the cycle you paid for, your configuration stays in place and you are not charged again. At the end of the cycle, the container drops to the Free plan (up to 10,000 requests) and the dedicated gateways are disabled. So you can leave your Stape configuration in place, cut on the platform side, while you check Oriva.

And your data at Stape?

Stape's data processing agreement provides that, at the end of the services, it deletes the personal data processed on your behalf, or returns it to you, at your choice, with a certificate. A container's logs are kept 10 days according to the annex of that agreement, and 3 or 10 days depending on the plan according to its pricing page.

What Stape does not say on the pages we read on October 13, 2026: how long it takes for your configuration to be deleted after a subscription ends, what becomes of the DNS record (CNAME) of your tracking subdomain once the container is deleted, and whether deleting the container at Stape also deletes the one in your Google Tag Manager account. For deleting the data, ask Stape before you cancel: its page does not say through which channel.

Advice from Oriva, not from Stape: once you are sure nothing uses it, remove from your DNS the record that pointed to Stape, and keep your .json export before you delete anything.

And the refund?

Stape publishes a refund policy whose windows run from a few days to 60 days depending on the plan (monthly or annual) and on usage (page updated August 10, 2026). Its terms and conditions and its help pages do not give the same windows: read the refund page before you cancel, and write to Stape's support with the account email, the container name, the date and the amount.

Payment at Stape is made in advance. With an annual subscription you have paid until the end of the year: one more reason not to rush the cancellation, and to leave Stape running on standby while you check.

What does it cost during the transition?

You pay Stape until the end of the cycle already paid, and the Oriva trial lasts 14 days: a card is requested, nothing is charged before the trial ends. The prices of each are on the Oriva, a Stape alternative page and on Pricing, with their date: we do not repeat them here so they do not age in two places.

Who doesn't need to migrate?

  • Your container serves more than ad conversions (analytics, third-party tags, data transformations). Oriva sends conversions to five destinations; it does not replace a server GTM container that does the rest.
  • You only advertise on Meta and your pixel loads fine. Stape's gateway may be enough, cheaper than Oriva for that single use: it is said in the comparison.
  • Your container runs well and someone maintains it. Changing tools has a real cost, and Oriva is not better because it is newer.

Oriva is for when you want several platforms without building a container yourself, or when the sales your pixel does not see are costing you conversions.

Start free trial

Would you rather we install it?

The done-for-you installation sets Oriva up on one of your domains: DNS, tracking code, one to 3 destinations and a test event checked per platform, for €199, $199 or £199, one time. Cutting Stape stays on your side: it is your account, and the right moment depends on your campaigns. The details are on the Pricing page.

Keep reading

Sources

Pages of stape.io read on October 13, 2026. They may have changed since: check them before you decide.