Video summary

Cómo Instalar la API de Conversiones en Cualquier Página Web

Main summary

Key takeaways

Technology

Summary (Technological concepts, features, and tutorial/guide flow)

Problem & motivation

  • The video argues that implementing Meta’s Conversions API is not optional. If it isn’t properly set up, you’re allegedly sending broken/incomplete “dirty” conversion data to Meta—while competitors use better data, leading to:
    • faster campaign optimization,
    • cheaper leads/sales,
    • more complete tracking visible in Meta’s admin.
  • It also claims many people wrongly think the setup is technical/complex/expensive and positions the video as a step-by-step approach that doesn’t require coding skills.

What the Conversions API is (and how it differs from the Pixel)

  • Meta Pixel: a small snippet installed on the website that tracks user actions after ad clicks, but it depends on the user’s browser.
    • Tracking can fail when cookies are blocked, ad blockers are used, or the browser has loading issues.
  • Conversions API: a server-to-server method where your server sends event data directly to Meta.
    • This makes it less dependent on cookies/browser behavior.
  • The video emphasizes they are not rivals:
    • Pixel captures what it can,
    • Conversions API reinforces/complements missing events.

Advantages of using Conversions API

  1. More information collected (less dependent on cookies/ad blockers/private mode).
  2. Stronger optimization signals for Meta’s algorithm to identify converters, improving:
    • cost efficiency (lower costs),
    • ability to scale results.
  3. Less reliance on Pixel, which is increasingly affected by privacy changes (e.g., iOS 14.5).
  4. Competitive advantage: many small/medium advertisers are still “pixel-only,” so a correct implementation should outperform them.

Warning / disclaimer about “easy” plugins

  • The presenter cautions against shortcuts/plugins that promise setup “in two clicks” (e.g., generic “Pixel your site” tools).
  • Claimed risks:
    • lack of real control,
    • weak event optimization,
    • possible duplicate events,
    • false sense of correctness (sending incorrect/incomplete/useless data).
  • Recommendation: use a clean implementation you understand, so you control what gets sent.

Tool mentioned (product feature + pricing/plan claims)

  • The tutorial uses One Tag by Hmuray (naming varies in subtitles: Ahmuray/Hmuray).
    • It claims you can implement Meta Conversions API and also support other platforms (e.g., TikTok, Google, etc.) within the same system/account.
  • Key differentiator claimed:
    • no need for technical knowledge,
    • no separate external server (uses their infrastructure).
  • Pricing/plan claims:
    • paid plans (starts around €10/month, per subtitles).
    • proper implementation is required; free options may not work correctly.

Event-volume expectations (as described)

  • For small projects, it’s claimed to be difficult to exceed ~100,000 events/month.
  • Plans may scale to hundreds of thousands or millions of events/month.

Step-by-step tutorial / guide outline (implementation method)

Prerequisites

  • A Meta Pixel already created in Meta.
  • A One Tag account.
  • A Google Tag Manager account (stated as free).
  • Use Google Tag Manager to deploy the tag code and manage events.

Steps in One Tag (setup)

  1. Select/create plan (claims a free trial exists).
  2. In the One Tag dashboard:
    • Add a pixel.
    • Choose pixel type (Facebook in the example).
    • Enter Pixel ID (from Meta Events Manager/settings).
    • Add a dataset identifier.
    • Generate and paste an access token from the pixel’s API/conversions section.
  3. Save to configure the Pixel inside One Tag.

Steps in Google Tag Manager (deploy tags)

  1. Install Google Tag Manager on the website:
    • Copy code for before </head> and after <body> (as described).
    • Notes WordPress/Shopify alternatives exist via plugins/apps, but encourages direct code.
  2. In GTM:
    • Go to Tags and create a new tag (e.g., “Meta Pixel and API”).
    • In the community template gallery, find and add the One Tag template.
  3. Configure the tag template:
    • Select which Meta event to implement first (example: PageView across all pages).
    • Choose to send Pixel only, API only, or both.
      • Presenter recommends both.
    • Set the Pixel platform ID (Pixel ID used).
    • Paste the One Tag API token.
  4. Set the trigger/activator:
    • Example: “All pages” so PageView fires site-wide.

Configuring additional events (example: lead conversion)

  • The video demonstrates creating a new event in One Tag/GTM for Lead:
    • Choose event type (e.g., Lead / identify/register success).
    • Configure the tag to send both Pixel + Conversions API.
    • Set trigger logic based on URL:
      • Example: fire when the user reaches a thank-you page
      • using conditions like URL contains “thanks” / “thank-you-video”.
  • Verification:
    • Use GTM preview mode to confirm both:
      • Pixel event,
      • Conversions API event,
    • and ensure they fire correctly on the intended page (example: the webinar thank-you page).

Scaling the approach

  • For additional conversion types (subscriptions, purchases, etc.), the presenter says you:
    • repeat the event + trigger configuration steps,
    • and can set everything up in minutes.

Main speaker/source (as implied by subtitles)

  • Hugo (referred to directly in the narration).
  • Mentions/credits:
    • Tool: One Tag by Hmuray (Ahmuray).
    • Platforms referenced: Meta, Google Tag Manager, Facebook Pixel, plus optional coverage for TikTok/Google (per tool claim).

Original video