Analytics Connector
Connect GA4 so profile activity can be measured against real site traffic and enquiries.
The analytics connector joins profile activity to what happened next on your site. Views, calls and direction requests sit next to sessions and enquiries, so you can tell activity from outcome.
What it does
Profile metrics stop at the profile. Views, searches, calls and direction requests are useful, but they describe activity on Google rather than outcomes in the business. A location can show rising profile views while enquiries fall, and nothing in the profile data explains it.
That gap becomes a real problem in reporting. An agency showing profile view growth to a client whose phone is not ringing is presenting a number that is technically true and commercially irrelevant, and clients notice that disconnect faster than anyone expects.
Connecting your analytics puts both on one timeline. Profile views next to sessions, direction requests next to enquiries. When the two move together you have a result. When they move apart you have something worth investigating rather than a number to defend.
It also settles the most common argument in local SEO reporting. Whether the work produced anything. That question is unanswerable from profile data alone and straightforward once the two sides sit side by side.
Everything you get
GA4 connected
Your own analytics, joined to your profile data rather than kept in two tabs.
One timeline
Profile activity and site behaviour on the same chart, over the same period.
Per location
Each site joined to its own traffic, not one blended total.
Calls and directions alongside sessions
Activity on the profile next to what happened on your site.
Enquiry tracking
Form completions and calls counted, because those are the outcomes that matter.
Gap detection
Flags where profile activity is rising and site outcomes are not.
In the report
Both sides in the same client document rather than two exports.
Period comparison
This month against last, on both sides at once.
Read only connection
It reads your analytics. It does not change anything in your GA4.
From setup to first result
- 1
Connect GA4
A read only connection to the property you already use.
- 2
Map locations to traffic
Each site to its own pages, so the join is per location rather than blended.
- 3
Confirm enquiries are tracked
If form completions and calls are not counted, the outcome half is missing.
- 4
Look at both sides together
Profile activity next to sessions and enquiries, on one timeline.
- 5
Investigate the gaps
Rising views with flat enquiries is the most useful thing this will tell you.
- 6
Put both in the report
A client who sees only profile numbers will eventually ask the obvious question.
- 7
Compare periods
Direction on both sides is what tells you whether the work is working.
What changes when you use it
- Reporting profile views on their own
- Blending all locations into one total
- Not tracking enquiries
- Explaining away a divergence
- Connecting the wrong property
- Profile views are activity, not outcome
- Clients notice the disconnect
- The gap is the useful signal
- Blended traffic hides location problems
- Untracked enquiries make it pointless
Profile views are activity, not outcome
A number can rise while the phone stays quiet, and profile data alone cannot explain why.
Clients notice the disconnect
Showing view growth to somebody whose enquiries are flat damages trust faster than a bad month does.
The gap is the useful signal
Views up and enquiries flat means something specific, and it is usually fixable.
Blended traffic hides location problems
One site can be carrying the total while three others do nothing.
Untracked enquiries make it pointless
If forms and calls are not counted, you have joined activity to more activity.
It answers the only question that matters
Whether the work produced anything, which profile data on its own cannot.
What it measures
- Profile views, calls and direction requests
- Sessions and users per location
- Enquiries per location
- Ratio of profile activity to enquiries
- Change on both sides period on period
- Locations where the two diverge
Reports you can send
Every output can be exported and carries your branding, never ours.
Joined timeline
Profile activity and site behaviour together.
Per location view
Each site against its own traffic.
Enquiry counts
Forms and calls, by location.
Gap flags
Where activity and outcome diverge.
Period comparison
Both sides, this period against last.
Report section
Ready for the client document.
Who this is built for
Answer whether the work produced anything, with data.
See which sites turn views into enquiries.
Compare activity and outcome per franchisee.
Find out whether rising views ever reach the phone.
Get more out of it
- Connect the property you actually use, not a spare one.
- Map traffic per location rather than reporting a blended total.
- Make sure forms and calls are tracked before you draw conclusions.
- Read the two sides together, never separately.
- Investigate divergence rather than explaining it away.
- Put both sides in the client report from the first month.
Reporting profile views on their own
It is activity, not outcome, and a client whose phone is quiet will say so.
Blending all locations into one total
One strong site can carry a total while three others do nothing at all.
Not tracking enquiries
Without forms and calls counted you have joined one activity metric to another.
Explaining away a divergence
Views up and enquiries flat is the most useful signal you will get. It is worth investigating, not defending.
Connecting the wrong property
A spare or a test property produces numbers that look real and are not.
By hand, or with this
| Doing it manually | With Analytics Connector |
|---|---|
| Profile views with no context | Activity next to outcome |
| Two tabs and a guess | One timeline |
| One blended traffic total | Traffic per location |
| Enquiries not counted | Forms and calls tracked |
| A number the client cannot feel | A number they can check against the phone |
| No answer to did it work | A direct answer |
- Connect your real GA4 property
- Map each location to its own pages
- Confirm forms and calls are being tracked
- Put profile activity and enquiries on one timeline
- Look for locations where the two diverge
- Add both sides to the client report
- Compare period on period from month two
One of 42 tools on the same plan
Every tool below is on the same plan at the same price. Nothing here is an extra, an upgrade or a separate subscription.
Rank & Visibility
Manage Profiles
Posts & Automation
Reviews & Reputation
Reports & White-Label
Questions people ask
Why connect analytics at all?
Because profile views describe activity on Google, not outcomes in your business. A location can show rising views while enquiries fall, and profile data alone cannot tell you why.
What does it actually join?
Profile views, calls and direction requests on one side, and sessions, users and enquiries on the other, on the same timeline and per location.
Does it change anything in my GA4?
No. The connection is read only. It reads your analytics and does not write to it.
Why does per location matter?
Because one strong site can carry a blended total while three others do nothing, and you would never see it.
What if my forms are not tracked?
Then fix that first. Without enquiries counted you are joining one activity metric to another and learning nothing.
What does it mean if views rise and enquiries do not?
It is the most useful signal you will get. Usually something between the profile and the enquiry is broken, and it is worth investigating rather than explaining away.
Should this go in a client report?
Yes, from the first month. A client shown only profile numbers eventually asks whether the phone rang, and you want that answer ready.
Every tool. One price. Nothing extra to buy.
$5.33 per location per month gets you Analytics Connector and the other 41 tools.