managed-components / managed-components/google-ads
Put all custom fields in the `data` query parameter automatically
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We would like to send custom fields set in the Zaraz remarketing tool interface to Google Ads and are wondering wether `payload.data` is the variable holding the custom fields content:
https://github.com/managed-components/google-ads/blob/98a05f12bb63a419bec39df26378a127e32b84d7/src/index.ts#L106
Is this correct? Is this line the part where the custom fields get merged in the parameters?
We are expecting to see custom field data set as parameters in Google ads in the segment creation section in Audiences as follows:

For some reason we do not receive the custom field value as a custom parameter to use in creating custom segment in Google Ads. What could be the reason? Could you give an example of how the URL looks like with custom fields?
Thank you very much indeed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at src/index.ts line 106 and inspect how payload.data is used when Google Ads parameters are assembled. Reproduce the request with custom fields from the Zaraz remarketing interface, then determine whether those fields reach the generated URL; done should include a confirmed explanation or a defined change for passing them through.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100