> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/marketing-optimization/google-ads-and-meta-keep-asking-me-to-add-more-events-and-parameters.-do-i-have-to-act-on-that.md).

# Google Ads and Meta keep asking me to add more events and parameters. Do I have to act on that?

I require more paramters in my tracking data according to my marketing platforms, is that correct?

**Short answer: usually not.** These notices are the platform's own wish list, not a sign that something is broken in your tracking. Your AdPage server-side setup already covers the events and matching data that matter most. Before you act on a recommendation, check what you are actually measuring, you can do that yourself in the AdPage platform.

Here a example of pageView extra parameters.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FybQeejfPO8p86RNE31zs%2Fimage.png?alt=media&amp;token=7aa1b12c-fec8-4249-9f5f-a83d08d2bfb3" alt=""><figcaption></figcaption></figure>

### Why do platforms keep asking for more data?

Advertising platforms are in a constant race for signal. Every platform wants to receive as much matching data as possible (identifiers such as click IDs, hashed email addresses or phone numbers) and as many events as possible, because more data helps their algorithms optimise your campaigns (and their revenue).

Three things are useful to keep in mind:

* **These prompts are the platform's own recommendations.** They appear inside the platform's dashboard and are designed to maximise the data that platform receives. That interest often lines up with spending more: the number of click IDs you can capture only grows as you advertise more through that channel.
* **Not every recommendation makes sense for your shop.** A platform might suggest sending an email address with an `add_to_cart` event, but at that point in the visit there usually is no email yet.
* **A warning is a suggestion, not a broken tag.** Seeing recommendations or "action needed" notices when you log in is normal. They reflect what the platform would like to receive — not the health of your AdPage setup.

{% hint style="info" %}
**Good to know.** Platform recommendations describe the platform's wish list, not a problem with your tracking. Before you act on one, check what is actually being measured.
{% endhint %}

### What does my AdPage setup already cover?

With server-side tagging through AdPage, your core measurement and matching are already strong from day one. Purchases, revenue, consent signals and the standard e-commerce events are collected server-side and shared with your connected platforms. For most shops this baseline already delivers solid matching quality, often better than the client-side setup the platform compares against.

In other words: you rarely need to chase every recommendation to have a healthy, well-matched setup.

### How do I check before I change anything?

Whenever a platform suggests an improvement, start by looking at what your setup already does. You can answer most questions yourself, directly in the AdPage platform.

1. **Open Monitoring.** Go to Monitoring to see which events and parameters are actually coming in. This tells you whether the data the platform is asking for is already there, partially there, or genuinely missing.
2. **Ask the AI assistant.** Ask our in-platform AI assistant, Brent, what a specific event, parameter or recommendation means for your setup and which options you have. It's the fastest way to understand a platform notice in the context of your own container.
3. **Read your setup analysis.** Your platform includes a ready-made analysis of your current tracking. Use it to see where you stand and where the realistic opportunities are, so you can prioritise instead of reacting to every notice.
4. **Confirm there are no delivery issues.** Check the platform status to confirm your data is being delivered correctly. If matching looks lower than expected, this rules out a delivery problem before you consider deeper changes.

### When does a recommendation become a real project?

Some requests go beyond server-side tagging. Filling specific parameters more completely, or adding custom conversions with your own values (for example a quote request valued at a fixed amount, or a sample request at 10% of the quote value) is usually possible within your existing container, the same way it is already done for Google Ads. But it comes with real dependencies:

* **Website & IT work.** To capture and pass extra data at the right moments in the visit, your website often needs custom development. Frequently the data simply doesn't exist yet at the point where the platform wants it.
* **Platform-specific.** What's possible, and what's actually worth doing, differs per marketing platform.
* **Trade-offs.** More data is not automatically better. There are pros and cons around accuracy, consent and privacy, and ongoing maintenance.

This is why improving a marketing platform is a data-consultancy question rather than a support question: it needs analysis of your goals, your site and your channels before anything is built.

{% hint style="info" %}
**Our recommendation: build once, reuse everywhere.** Design every measurement as a solid GA4 base event first, then reuse that foundation for your other channels (Google Ads, Meta, Pinterest, TikTok). One well-designed event set feeds every platform, instead of rebuilding measurement per channel.
{% endhint %}

### Who builds it if my website needs changes?

For genuine measurement projects that need website changes, new events, richer parameters, custom conversion values, AdPage works with implementation partners. They can scope the website and IT work together with the platform-specific configuration, so the result is reliable and maintainable. Reach out to us and we'll point you to the right partner for your stack.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adpage.io/faq/marketing-optimization/google-ads-and-meta-keep-asking-me-to-add-more-events-and-parameters.-do-i-have-to-act-on-that.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.