Google Business Profile setup for MTOs
Google optimises towards whatever you send it. Send registrations and it buys registrations, most of which never verify, so the conversion import has to reach the first transfer itself.
Remittance only · Imports reach first transfer · Approval stays with Google
Google Business Profile setup for exchange houses covers the accounts, the tags and the conversion imports that let Google buy actual senders rather than signups. Ads, Analytics, Tag Manager and Search Console are built and linked, the financial services verification pack is prepared, and every conversion is tested twice over before any of the budget goes anywhere near a campaign.
What changes in the account
Most remittance accounts get built for the launch date and never for the reporting. Four things change.
Bidding on signups
Google buys the cheapest registrations, and they never verify.
Bidding on transfers
First transfer is imported back, so bidding follows the money.
Verification refused
The account is paused, and nobody knows which document is missing.
Verification prepared
The documents, the domain and the regulator details go in together.
Everyone is an admin
Six agencies hold owner access and nobody keeps a record.
Access is documented
Who owns what, and at what level, written down and dated.
Tags never checked
The conversion counts twice and the reporting looks superb.
Tags proven first
Every conversion fires once, with the value it should have.
What the whole setup covers
Four rows of work, run in order. Nothing gets launched before every conversion has been proven first.
What actually gets built first
It is plumbing, it is dull, and it decides a lot of things. Create, structure, connect and validate the Google marketing infrastructure required to run and measure remittance customer acquisition.
- Ads account built properly first
- GA4 property and the streams set
- Tag Manager container built out
What Google actually gets told to buy
The click is not the outcome that matters. Google Ads Click → Registration → KYC → First Transfer. This can materially improve campaign optimisation compared with optimising toward registrations alone.
- Registration imported as a step
- KYC completion imported as well
- First transfer sent back in too
The verification, and its limit
Documentation, domain details and regulatory information get prepared and submitted on your behalf, and the waiting afterwards is the part that nobody can shorten. Approval remains under Google's control.
- Advertiser verification is prepared
- Business documents gathered up
- Domain and regulator details sent
Access, and then proving the tags
Admin roles, agency access and developer access are documented, so the account survives the day somebody leaves. Every conversion is fired once in a test before the first campaign ever runs.
- Owner access always kept in-house
- Agency roles documented as well
- Deduplication is checked properly
What you actually receive
Six artefacts, all of them yours to keep. The access record is the one nobody ever has.
Account structure map
Which accounts exist, who sits under whom, and which markets each one of them actually covers.
Conversion action set
Every conversion action, its value, its window and whether it counts as a primary one or not.
Tag manager container
Every tag, every trigger and every variable, exported so it can be moved or audited later on.
Offline import feed
How the first transfer finds its way back into Google, and how often it happens in practice.
Access and roles doc
Who holds which role in every account, and who gets removed the moment they leave the company.
Developer setup guide
What your own developers have to implement for the web, the app and the server-side events.
How the setup work runs
Four stages, run in order. The imports are built before the very first campaign ever goes live.
The accounts that nobody wants to build
Ads, Analytics, Tag Manager and Search Console are created in your own name, with billing, access and structure agreed before anything else.
- 01Ads account created in your name
- 02Manager account where it is needed
- 03GA4 property and the data streams
- 04The Tag Manager container built
- 05Search Console verified as well
What actually comes back from the funnel
Registration, KYC completion and first transfer are imported as offline conversions, so bidding can follow the sender rather than the signup.
- 01Offline imports set up properly
- 02GA4 linked to your Ads account
- 03Enhanced conversions where fit
- 04App events wired through Firebase
- 05YouTube connected if it is used
All of the financial services paperwork
The advertiser verification pack is assembled, submitted and chased, though the decision and the timing both sit entirely with Google itself.
- 01Documents gathered in one place
- 02Domain ownership properly evidenced
- 03Regulatory details are supplied
- 04Submission tracked to a decision
- 05No approval date ever promised
Whether the numbers can all be trusted
Every conversion is fired in a test, checked for duplicates and matched against the analytics, before a single campaign is switched live.
- 01Tag firing checked one at a time
- 02Conversion values all verified
- 03Duplicates found and then removed
- 04Attribution settings all reviewed
- 05Setup guide handed to the devs
What the work actually does
Fifteen groups of work sit behind the service, and these twelve are what actually gets built first.
Ads account setup
Structure, billing and access
Manager account
For multiple markets or brands
GA4 property
Streams, events and conversions
The Tag Manager
Container, tags and triggers
Search Console
Verified, with the sitemap in
Conversion tracking
Registration, KYC, first transfer
Enhanced conversions
Where the privacy review allows
Offline imports
First transfer sent back to Google
App campaign setup
Firebase, app events, deep links
Verification support
The pack, prepared and submitted
Access governance
Roles, owners and the record
Conversion QA
Fires once, with the right value
Three ways to buy this
One of these will fit, whether nothing exists yet or six old agencies still hold the keys.
Complete account build
The accounts, the tags, the imports, the verification and the QA, all delivered just the once.
- Fixed fee, agreed before we start
- Accounts opened in your own name
- No approval date is ever promised
Conversion import build
Only the offline import itself, from the click through to the first transfer and back again.
- One fixed fee, two weeks total
- Works with your existing setup
- The import feed is handed over
Complete account audit
What is broken, what fires twice, and who still holds the access that they should not have.
- One week, priced before we start
- No obligation to rebuild after
- Every broken tag is listed out
Four steps to going live
One week of building, and then the imports. Verification can take longer than the whole build does.
Open the accounts
WEEK 1Ads, Analytics, Tag Manager and Search Console, all opened in your own company name.
Wire the events
WEEK 2Conversions defined, tags built and the offline import connected to your own CRM feed.
Submit the pack
WEEK 2-6Documents, domain and regulatory details are submitted, then chased until it is decided.
Test then handover
WEEK 3Every conversion fired once, then the guides and the access record handed over to you.
How results get reported
No client figure appears without written permission. These three are facts about how the work is run.
Questions operators ask first
Answers come first. Where the honest answer is no, it says no and explains what to do instead.
Both. An app-led operator needs Firebase and the app events wired, and an agent-led one needs the branch and call conversions counted too.
Yes. The offline import runs from whichever CRM holds the first transfer, using the click identifier your site already stores.
Yes. Corridor travels as a parameter on the imported conversion, so bidding can favour the routes that actually pay rather than the loudest ones.
Yes. Google Business Profile setup for exchange houses is all that gets built, so the verification pack and the KYC events are expected, not improvised.
The financial services verification pack is prepared to Google's own requirements. Approval remains under Google's control. Licensing and AML go to a qualified adviser.
Domain access, company documents, the regulator details where they apply, your CRM export route, and whoever can approve the billing.
One week to build and wire, then verification. Google decides that timeline, and anybody promising a date has not read the policy.
Yes. KYC completion and first transfer are imported as conversions, so the ad account learns from the same events your funnel reports on.
Yes. A manager account holds one account per market where that is needed, with the same conversion definitions across all of them.
Partly. Repeat transfers can be imported as a separate conversion, which lets remarketing audiences build on senders rather than on visitors.
The offline import carries the click identifier through registration and KYC to the first transfer, so cost per first send is reported by campaign.
Monthly: cost per registration, cost per verified customer and cost per first transfer, by campaign, by corridor and by device.
This can materially improve campaign optimisation compared with optimising toward registrations alone. Google bids for the outcome you actually import.
Wasted spend removed once bidding follows verified senders. Google Business Profile setup for exchange houses usually pays back inside the first month of spend.
Indirectly. Better acquisition brings senders who intended to send, and those senders repeat more often than the ones bought on a cheap click.
Operators, remittance apps and payout platforms on the roster
Marks appear once written permission is on file for each operator.
Import the transfer, then spend
While the import is missing, Google buys the wrong customer with your money. A fixed-fee growth audit will say exactly what is missing and why.
You keep the accounts and the access whether or not we continue.