Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / MariaDB / MariaDB to Google EC for Leads

    MariaDB tables into Google Ads, built for Google Enhanced Conversions for Leads.

    Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then sends down-funnel lead milestones matched to the originating Google click so Google Ads sees lead conversions without an export.

    Talk to our team Explore the setup

    mariadb -> google-ec-leads :: live

    1. ● mariadb → google.leads :: live
    2. > read lead_pipeline rows=33,485
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 29,132 matched

    WHAT THIS ENABLES

    MariaDB to Google EC for Leads

    Google EC for Leads for MariaDB: Signals sends down-funnel lead milestones matched to the originating Google click straight from your MariaDB tables, hashed and consent-screened each time the read runs.

    • Signals sends down-funnel lead milestones matched to the originating Google click, reading your MariaDB tables each time the read runs.
    • Lead-value signals matched to the paid click, with no export step out of your MariaDB tables.

    WHAT FLOWS WHERE

    MariaDB to EC for Leads, mapped.

    Each sync hands the qualified-lead and pipeline signals from your MariaDB tables to Signals, which hashes and filters every record, then Google Ads' Enhanced Conversions API logs the lead conversions for GCLID and hashed-email matching.

    Each sync hands the qualified-lead and pipeline signals from your MariaDB tables to Signals, which hashes and filters every record, then Google Ads' Enhanced Conversions API logs the lead conversions for GCLID and hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Google lead-gen advertisers bidding past the first form submit, working out of MariaDB tables and views.

    Engineering teams running MariaDB who need lead-value bidding fed by the stages your pipeline actually reaches out of MariaDB tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MariaDB tables you name, mapped to Google Ads' Enhanced Conversions API and tuned for GCLID and hashed-email matching.

    2. Map

      Columns from your MariaDB tables align to Google Ads' Enhanced Conversions API in the visual mapper, hashed as the read runs and checked for GCLID and hashed-email matching.

    3. Deliver

      Each time the read runs, Signals reads your MariaDB tables and sends down-funnel lead milestones matched to the originating Google click, reads only the records changed since the last run, with GCLID and hashed-email matching watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lead-value bidding fed by the stages your pipeline actually reaches from your MariaDB tables, delivered each time the read runs.

    Lead-value signals matched to the paid click out of your MariaDB tables, delivered each time the read runs without read load on the database climbing.

    Match feedback on GCLID and hashed-email matching from Google Ads' Enhanced Conversions API each run, tied back to your MariaDB tables.

    ON THE WIRE

    What EC for Leads actually receives.

    signals :: mariadb.google-ec-leads :: wire

    1. ● signals :: event payload
    2. > POST /conversion_action source=mariadb.lead_pipeline
    3. gclid "Cj0KCQjw…" · conversion_action "sql_reached"
    4. conversion_value 7 · currency GBP
    5. hashed_email sha256 "9c41af…"
    6. ✓ accepted match=gclid+hashed_email
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MariaDB

    MariaDB to Meta Conversion Leads

    Meta CAPI for CRM for MariaDB: Signals reports lead-stage progress so Meta bids toward…

    Learn more

    from MariaDB

    MariaDB to TikTok CRM

    TikTok CRM Integration for MariaDB: Signals reports pipeline-stage changes to TikTok as…

    Learn more

    same use case

    ActiveCampaign to Google EC for Leads

    ActiveCampaign to Google EC for Leads: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Enhanced Conversions for Leads

    Datahash pushes hashed user data from your CRM back to Google Ads so lead-based campaigns…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MariaDB Google EC for Leads sync run?

    You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into Google Ads. Since Signals reads only the records changed since the last run, lead-value bidding fed by the stages your pipeline actually reaches keeps pace and engineering teams running MariaDB watch GCLID and hashed-email matching. One scoped connection sets it up, cadence adjustable later.

    What match rate should a MariaDB-sourced Google EC for Leads batch expect?

    Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Enhanced Conversions API pinpoints GCLID and hashed-email matching, the number engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to Google EC for Leads, in production this week.

    Talk to our team All MariaDB use cases