managed-components / managed-components/google-ads

Not actually server side ?

Open
#9 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Hello,

Looking at the code implementation, I'm not actually seeing any use of manager.fetch. There are only calls being done with the client.fetch API.

If I understood correctly how managed components works, this means that this doesn't actually send server side requests to google, but will simply send the requests from the browser ? I can actually see those requests being sent to google when I inspect the network tab, and the Zaraz debug tool doesn't log any server side requests being sent, only client side requests.

I know a clear documentation on how to implement a custom server side tracking for Google Ads is pretty much non-existent (I couldn't find any official resource on this, everything points to using Google Tag Manager).

So is it actually possible to do proper server side tracking for Google Ads ? Or are we doomed to keep that tracking part client side only ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the TypeScript implementation and trace the manager.fetch and client.fetch entry points. Use the browser network tab and Zaraz debug tool observations described in the issue to determine which requests are client-side versus server-side. Done means establishing whether proper server-side Google Ads tracking is supported and documenting or scoping the required change.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.