“Did You Change How Conversions Are Counted Last Month?” How to Stay Ready When Consent Mode Changes Your Numbers

“Did you change the conversion definition or measurement conditions last month?”

If you manage a company website and also work with an ad agency, this question can feel uncomfortably familiar.

Conversions went up.
Or they suddenly dropped.
Was it because of ad performance?
A website change?
A tag update?
Or a consent setting?

For the person who has to explain the numbers at the end, not being able to answer immediately can be stressful.

From June 15, 2026, the way data flows between Google Analytics and Google Ads changes. The handoff of ad data, which had previously been controlled through both “Google Signals” and “Consent Mode,” is being consolidated onto the Consent Mode（ad_storage）side.

When we read this announcement, the first thing we checked was not the detailed behavior of the feature.

It was this:

“Who confirms this on our side, and where do we record it?”

When tags, a CMP, an ad agency, and an internal web manager are all involved, the settings change itself is only one part of the work. What matters just as much is whether the team can explain what changed before and after.

In this article, we’ll walk through the check sheet and recording flow we prepared for the Consent Mode consolidation.

---

Why This Problem Happens

Background 1: Measurement Changes Are Not Just a Tag Owner’s Task

Before June 15, data sent between Google Analytics and Google Ads passed through two main gates.

One was “Google Signals” on the Google Analytics side.
The other was “Consent Mode” on the Google Ads side.

From June 15 onward, Consent Mode（ad_storage）becomes the sole control. Google Signals is reduced to a role within Google Analytics, tied to behavior reports for logged-in users.

This is where a common operational gap appears.

The tag owner updates the settings.
The CMP owner checks consent behavior.
The ad agency looks at performance in the ad platform.
The in-house web manager explains conversion numbers in the monthly report.

Each person may be doing their own work correctly. But if the change date, reason, and before-and-after numbers are not recorded, the team cannot explain later why the numbers moved.

Background 2: Before-and-After Numbers Easily Get Separated

We made this mistake once with another tag-related change.

The settings update itself was completed by the tag owner. But at the end of the month, when the agency asked, “Did you change the conversion definition last month?”, no one could immediately answer when, what, or why it had changed.

The change had been completed.
But there was no record of the change.

When this happens, it becomes difficult to separate whether a conversion swing came from actual campaign performance or from a change in measurement conditions.

A measurement change is not finished when the tag is updated.

At minimum, the following four items need to stay together:

• the numbers before the change
• the date of the change
• the reason for the change
• the numbers after the change

The Consent Mode consolidation is exactly the kind of change that tests whether this record-keeping habit exists.

---

Steps to Prepare for the Change

STEP 1: Make the Current State Visible

The first step is to make the current settings and possible impact areas visible.

We prepared a check sheet that we open whenever we touch measurement conditions. For this Consent Mode consolidation, our check items include the following:

1. Did we confirm the state of Consent Mode（ad_storage）on the Google Ads side?
2. Is the CMP’s consent capture correctly linked with ad_storage?
3. Are there any reports or audiences that assumed Google Signals was in place?
4. Did we take screenshots of conversions and key metrics before the change?
5. If we have users in the EU, did we confirm whether consent-related notice is required?

The fifth item is especially easy to overlook.

For sites with EU users, this change may relate to how consent is captured and communicated. We do not leave this decision to the web manager alone. We include legal and management confirmation as part of the check item.

We register these items in the MONJI+ checklist feature. Since the checklist can be called up from the feedback creation screen, it becomes easier to make sure the same items are reviewed every time.

STEP 2: Record and Organize It as Part of Monthly Operations

Creating a check sheet is not enough.
The important part is to keep the change work itself as a record.

In our case, we create one piece of feedback in MONJI+ for the Consent Mode consolidation work. We assign it to the tag owner and add a due date and priority.

This prevents the question of “who is doing what by when?” from becoming vague.

Feedback with upcoming due dates appears on the My Page dashboard, so we can see what remains before the consolidation date.

In addition to the checklist, we also keep change history in the project Wiki.

We do not write long meeting minutes.
We simply record the following line by line:

“when, who, what, and why it changed.”

Because the tag owner, CMP owner, and ad owner are all in the same project, each person’s work is accumulated in one place in chronological order.

With this in place, when the agency asks, “Did you change the measurement conditions last month?”, we can answer while looking at the Wiki.

“On June X, we shifted to the ad_storage side. The reason was to prepare for the Consent Mode consolidation.”

That one sentence makes the conversation much smoother.

STEP 3: Compare Several Months of Results Before Drawing Conclusions

With measurement changes like Consent Mode, it can be risky to judge from numbers immediately after the change.

Even if conversions move, it may not be clear right away whether the cause is the settings change, ad delivery, or user behavior.

That is why we try to keep conversion numbers and key metrics visible across several months before and after the change.

In our workflow, post-change conversions and key metrics can also be checked within the same project through the Google Analytics integration.

Changed it.
Looked at the numbers.
Recorded it.

Keeping these steps connected makes it easier to look back later.

For an external partner such as an ad agency, we can also use a public link to share only the feedback currently in progress.

This reduces the need to repeatedly explain the status out loud and helps everyone look at the numbers with the same context.

---

What Changed in Practice

After combining the checklist and Wiki, conversations with the agency became noticeably faster.

Before, whenever conversion numbers moved, we had to ask around:

“Did anything change on the tag side?”
“Has the CMP been checked?”
“When did we look at the GA settings?”
“Who handled the work?”

Now, we first check the Wiki.
Then we check the feedback history.
If necessary, we look at the before-and-after conversion numbers and key metrics.

This order gives us a clearer path.

As a result, it has become easier to separate whether a swing in the numbers came from a measurement change or from actual performance.

Of course, not everything can be judged automatically. Still, having the context in one place makes explanation much faster.

---

Notes and Limitations

A tool does not automatically guarantee that Consent Mode settings or consent capture are correct.

Each site has different conditions.

Which countries do users come from?
What type of consent is being captured?
Is the CMP correctly linked with ad_storage?
Which areas require legal or management confirmation?

These are decisions that the team responsible for the site needs to own.

Checklists and Wikis are only the foundation for making that decision. They do not make the decision on behalf of the team.

That is why we draw a line.

We let the system help us organize the check items.
But we keep the final “this is how we proceed” decision in our own hands.

Even when part of the work is handled with an ad agency, the change history and responsibility for explaining the numbers should not be completely outsourced.

The Consent Mode consolidation became a good opportunity for us to reaffirm that line.

---

MONJI+, the WebOps Platform Born from the Field

As this example shows, website operation often requires more than simply changing a setting.

Teams also need to confirm the impact, record the history, and share the context with the right people.

MONJI+ is a WebOps platform created to solve the challenges we have felt firsthand in the field.

MONJI+ brings the people involved in website operation together into one team and supports work across every phase of website operation.

From the start, we have never aimed to build a “finished product.”

The challenges truly worth facing exist in the field of website operation. That is why we continue to listen to the real voices of people working there.

By taking in each voice and resolving small points of friction through updates, new features have grown out of real operational challenges.

Through that accumulation, MONJI+ has become supported by users across 77 countries.

▼ Learn more about MONJI+ here
https://monji.tech/plus/

A world where people working in website operation can say, with pride, “I love this work.”

▼ To make that real, we are waiting to hear your voice
https://monji.tech/plus/co-creation/

---

Summary

The Consent Mode consolidation should not be treated as just another settings update.

For in-house web managers who stand between tags, CMPs, and ad agencies, it is important to keep a record of who changed what, when, and why.

In this article, we introduced the flow we use:

• confirm the state of Consent Mode（ad_storage）
• check whether the CMP is correctly linked with ad_storage
• review reports or audiences that assumed Google Signals
• save screenshots of conversions and key metrics before the change
• check consent-related notice requirements if there are EU users
• create feedback with an owner, due date, and priority
• record the change history in the Wiki
• compare post-change numbers in the same project

When someone asks, “Did anything change last month?”, the goal is to answer from records, not memory.

Preparing a simple check sheet is a good first step toward making that possible.