Allow setting query parameters without prefix in tool settings
@omarmosid is already working on this.
Since Sep 14, 2023.
Assessment
This issue has not been assessed yet.
Description
Problem Description
Currently there is a limitation in the ability to set query parameters without a prefix at the component / event level using the tool settings menu. The only option available is to set definitions that are automatically prefixed with an epn. or ep. prefix. This limitation makes it impossible to set important query parameters such as "Ignore Referrer (&ir)" or "Is Debug (&_dbg)".
Suggested solutions
-
Introduction of "additionalQueryParams" field
A simple solution to address this limitation would be to provide an additional preference field called "additionalQueryParams" in the tool's preference menu. This field would allow users to add query parameters as-is, without any additional prefixes. It's important to make sure that the settings data takes precedence over the event/generated data. -
Implement argument selection drop-down
A more user-friendly and robust solution would be to implement a feature that allows users to select individual arguments from a drop-down list in the tool settings menu, eliminating the need to manually type them in. The GA4 Measurement Protocol Cheat Sheet (https://www.thyngster.com/ga4-measurement-protocol-cheatsheet/#) provides a good reference.
Expected Results
Implementing either of these solutions would greatly improve the flexibility and usability of the component. It will allow users to set arbitrary query parameter values using JSONata. This will help prevent forking of the component, which would lock users out of further updates.
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from managed-components/google-analytics-4
-
User ID gets ignoredOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
managed-components/google-analytics-4#40 · 7 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
managed-components/google-analytics-4#39 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
managed-components/google-analytics-4#38 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
managed-components/google-analytics-4#25 · 1 comment ·
All issues in managed-components/google-analytics-4
Similar issues
-
area/core status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
google-gemini/gemini-cli#29602 ·
Maintainers usually reply within 1 day
-
area: backend enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
snapotter-hq/SnapOtter#1879 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Tencent/BrowserSkill#390 ·
Maintainers usually reply within 1 day
-
good first issue status: needs triaging type: bug version: 2.0
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
medusajs/medusa#17094 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day