Integrate Convert Experiences with Tiendanube
Run A/B Tests on Tiendanube (Nuvemshop) with Convert Experiences Using Google Tag Manager
| Author: | Dionysia Kontotasiou |
THIS ARTICLE WILL HELP YOU:
- Get an Introduction
- Connect Google Tag Manager to your store
- Install the Convert tracking code through GTM
- Set up revenue and purchase tracking
- Create and launch your first experience
Introduction
Tiendanube (Nuvemshop in Brazil) is a hosted e-commerce platform for Latin America. Once Convert is loaded on the store, you can run A/B, split URL, multivariate and personalization experiences on every storefront page: home, category, product, search, cart and content pages.
Convert Experiences can run on a Tiendanube storefront through Google Tag Manager, because Tiendanube has no field for pasting third-party JavaScript directly. This guide covers the full setup: connecting GTM, loading the Convert tracking code, measuring purchases, and launching a first test.
Step 1: Connect Google Tag Manager to your store
Tiendanube asks only for your container ID; you never paste the GTM snippet yourself. The steps below follow Tiendanube's GTM guide.
- Sign in to Google Tag Manager and create an account, or open an existing one.
- Create a container named after your store and choose Web as the target platform.
- Close the install-code popup and copy the container ID (
GTM-XXXXXXX) from the top of the workspace. - In your Tiendanube admin, go to Configuración > Códigos externos.
- Paste the ID into the Google GTM ID field in the Google Tag Manager section. If the field is missing, contact Tiendanube support to have it enabled.
- Click Guardar cambios.
To confirm the connection, click Preview in GTM, enter your store URL with https://, and check that Tag Assistant connects when the store opens.
Step 2: Install the Convert Tracking code through GTM
The Convert tracking code goes into one Custom HTML tag that fires on every storefront page. The method follows Convert's own GTM installation article.
- In Convert, open your project and go to Configuration > Environments & Tracking Code. Open the menu for your environment, choose Install Code Snippet, and copy the snippet.
- In GTM, go to Tags > New and choose Custom HTML as the tag type. Name it "Convert Experiences - Tracking Code".
- Paste the line below first, then your own Convert snippet directly under it:
<script type="text/javascript">
var _conv_prevent_bodyhide = true;
</script>
<!-- begin Convert Experiences code -->
<script type="text/javascript" src="//cdn-4.convertexperiments.com/v1/js/ACCOUNT_ID-PROJECT_ID.js">
</script>
<!-- end Convert Experiences code -->
- Replace the second block with the exact snippet from your Convert project. The
ACCOUNT_ID-PROJECT_IDvalues above are placeholders. - Under Triggering, choose Initialization - All Pages so the tag fires as early as GTM allows.
- Under Advanced Settings, set a high Tag firing priority (for example 100) so Convert runs ahead of other tags on the same trigger.
- Click Save, then Submit > Publish and Create Version.
Step 3: Set up revenue and purchase tracking
Convert's standard revenue snippet will not work on Tiendanube, because it must run on the purchase confirmation page after the main tracking code (Convert revenue guide) and Tiendanube blocks Custom HTML in checkout.
Use the two options below instead.
| Option | Effort | Revenue in Convert reports? | Best for |
|---|---|---|---|
| A. Storefront goals in Convert | Low | No, conversions only | Every store, from day one |
| B. GA4 integration | Low to medium | In GA4; in Convert only if your test order confirms it | Stores already using Tiendanube's native GA4 |
Option A: Storefront goals
These goals fire on pages where Convert runs, so they work as soon as Step 2 is published.
- Add to cart: a click goal on the product page's buy button.
- Cart reached: a page-visit goal matching your cart URL.
- Checkout started: a click goal on the cart's "Iniciar compra" button. This is the last shopper action Convert can see directly.
Option B: GA4 integration
Convert's GA4 integration sends an experience_impression event with an exp_variant_string parameter in the form CONV-[experience_id]-[variation_id] (Convert GA4 guide). Tiendanube's native GA4 integration sends the purchase event, so GA4 holds both halves.
- Connect GA4 in Tiendanube under Configuración > Códigos externos, using the native field. Do not also add GA4 through GTM, or events will double.
- In Convert, open Project Configuration > Integrations, check Google Analytics, select Google Analytics 4, and sign in to pick your property and data stream.
- Activate an experience and click Create GA4 Audiences to get one audience per variation.
- In GA4, register
exp_variant_stringas a custom dimension and compare purchases and revenue per variation in Explore. - In Convert, enable GA4 revenue tracking in the project configuration and import the GA4
purchaseevent as a goal.
Step 4: Create and launch your first experience
Start with a simple A/B test on a product page, since it gets steady traffic and sits one click from the cart.
- In Convert, click New Experience, choose A/B, and enter a product page URL from your store.
- In the Visual Editor, change one element in the variation, for example the buy-button text or the position of shipping and installment information.
- Under Locations, target all product pages with a URL rule that matches your store's product URL pattern.
- Under Goals, add the storefront goals from Step 3 and, if you set it up, the imported GA4 purchase goal.
- Use Preview or the force-variation links to check each variation on desktop and mobile.
- Set the traffic split and click Activate.