Brand Colors & Typography for Gulf Markets | MartGain

Meta description: A practical audit for property and interior brands: review the problem, queries, tracking, landing page, and handoff before changing spend or ads.

Start with the decision a customer should make

An ad account audit is not a tour of every settings screen. For a property developer, broker, or interior firm, it starts with a business decision. Should a person request a viewing, ask about a project, book a call, or be qualified by budget and location? Each decision creates a different path. Clicks alone cannot tell you whether the account is working.

Write a problem card before touching settings. Include the offer shown to the visitor, the city or area, and the property type. Add the requested action and the definition of a qualified inquiry. A project-page view is an early signal; a submitted viewing request is closer to the commercial outcome. Keeping those actions separate prevents a mixed conversion column from hiding the real issue.

Also write what the ad must not promise. Do not invent a unit size, price, handover date, or availability. Do not imply that a searcher has a particular financial status. The problem card is the reference point for every later audit decision.

Start the audit with the account and the journey behind the traffic, not with one number in a report. Our Ad Account Audit service helps organize settings, messages, and destinations before changes are proposed.

Build a timeline before looking for a culprit

Open Change history and record when the campaign was created and when budgets, targeting, ads, or conversion actions changed. Google describes Change history as a record of account, campaign, ad group, and ad edits over a historical period (C-08). Teams can relate those edits to what happened later. A timeline does not prove causation by itself, but it prevents a conclusion based on one screenshot.

Use five columns: date, change, stated reason, evidence after the change, and interim decision. If a broad term was added and irrelevant property inquiries appeared later, record the sequence without declaring that the edit caused the result until the evidence supports it. Keep a copy or recoverable record of the previous setting and name the person who can restore it.

Review the account structure from top to bottom

Check the relationship between the account, campaigns, ad groups, ads, and landing pages. Each campaign should have a readable objective, such as viewing requests or calls. Reflect location and property type in the structure when they change the promise or the destination. Copying one campaign across every city and only changing its name can produce an ad that no longer matches inventory or the page.

For each ad group ask three questions: what search theme does it serve, does the ad state that theme clearly, and does the page explain the same offer? Google recommends matching ads and keywords to the landing page (C-09). It also recommends a mobile-friendly page with a clear action and useful content. This is a relevance test, not a keyword-stuffing exercise.

Set a change boundary. Do not alter structure, budget, and page copy on the same day if you want to learn what mattered. An audit records the proposed decision and its evidence; it does not turn into a batch of untraceable edits.

Read search terms before adding exclusions

The search terms report shows queries that triggered ads and can reveal irrelevant terms for negative-keyword decisions (C-01). Export a sample that represents locations, periods, and ad groups. Classify each query as viewing or purchase intent, early research, outside the service area, or unrelated meaning.

Do not turn every broad query into a negative keyword. Check the match type first because match behavior changes what a term blocks in future queries (C-03). “Interior design” could be relevant to a fit-out firm but irrelevant to a ready-unit sales campaign; the offer determines the decision.

Record the reason and the scope of every exclusion. Separate a term that blocks one meaning from a term that blocks an entire audience. Revisit the list when the inventory, locations, or pages change. The aim is a clearer inquiry for the sales team, not simply fewer clicks.

Separate a tag’s presence from a valid conversion

A Google tag can appear in source code while a viewing request still fails to become a usable conversion. Use Tag Assistant to check the Google tag and its events (C-06). Then inspect each conversion action and its status. Google’s troubleshooting guidance distinguishes states such as active, needs attention, misconfigured, awaiting conversions, and removed (C-07). These labels describe diagnostics; they are not a quality score for the campaign.

Create a small event matrix: project-page view, form start, form submit, call request, and booked viewing. For each event write the trigger, the data received, the destination record, and whether it belongs in the Conversions column or remains an observation. Prevent a thank-you page refresh from firing a second submission. If two systems fire the same event, find the duplicate source before interpreting numbers.

Google’s enhanced-conversion guidance describes diagnostics and correctly configured user data (C-04). Collect only the fields required for the stated purpose. Respect the applicable consent process. A sound audit records what could not be verified instead of calling tracking “healthy” because one tag was found.

Test the page that receives the inquiry

The final URL should lead to a relevant page on the same domain and match the visitor’s expectation (C-02). Open the ad as a customer on a phone. Do they see the project or property type named in the ad? Is the approved price range or availability information present? Is the next action obvious? Does the form ask only for what the follow-up team needs?

Make sure the action is not buried under a long introduction. Test both Arabic and English when both exist, including direction, field order, and labels. Google recommends testing the mobile destination and keeping the mobile action aligned with the ad (C-05). If the ad promises a call, do not send the visitor to an unclear form; if it promises a viewing, make location and scheduling understandable.

Test on a slow connection and record visible or functional errors. Do not blame the ad before confirming that the page opens and the form reaches the right team. Keep evidence in the internal audit file without exposing personal data.

Deliver a report that selects the next decision

A useful report is not a long error list. Divide findings into four layers: measurement blockers, inquiry blockers, experiments, and deferrable work. For each finding include evidence, likely impact, proposed action, owner, and the acceptance check.

For example: “The form-submit event fires twice when the thank-you page is refreshed.” Evidence is two records from one test submission. The action is to protect the event or change its trigger; acceptance is one conversion after a repeat test. Another example is “The ad names a project while the page shows a generic catalogue.” Evidence is a side-by-side text comparison. Acceptance is message and destination alignment in both languages.

Do not insert an expected cost or improvement percentage without account data. If the sample is small, say so. If the decision is between two pages, write one hypothesis and one measure for each test, then set a review window. The audit becomes executable rather than a general opinion.

Use a release gate before any change

Before accepting the deliverable, ask:

1. Is the business problem and its representative event written clearly?
2. Does Change history explain what changed and when?
3. Is the search-term sample classified, with a reason and match type for each negative keyword?
4. Is there one source for each conversion event, or are tags duplicated?
5. Do language, location, property type, and action match the ad on mobile?
6. Does the inquiry reach an owner with the source and property context?
7. Which statements remain unverified or limited by the available data?

Google recommends removing legacy or duplicate tags and keeping sitewide tagging consistent to avoid duplicate counting (C-10). Therefore, finding a GTM container or Google tag is not an automatic pass. The pass requires a test from click to recorded inquiry. Use test data, inspect the event once, and keep the test separate from a real customer request.

The deliverable worth keeping

A good ad account audit leaves a decision map. It shows the problem, where the evidence appears, what should be fixed first, and what should wait for better data. For property and interior brands, the map should connect the ad to an understandable viewing request and a fast mobile page. It should also give the sales team a clear handoff.

Do not change budget simply because a dashboard looks worrying. Start with journey integrity, then review queries, tracking, and page alignment, and finally write one measurable experiment. If a point cannot be proven, keep it as an explicit gap. That is how an ad account audit becomes a reviewable decision file instead of a vague redesign of the account.

For the preceding step in preparing a reviewable campaign, read A reviewable ad campaign journey before separating an account issue from a page issue.

Once the account is organized, make measurement reliable enough to review every step. Explore Analytics & Conversion Tracking Setup when clicks, requests, and outcomes need one connected view.