Remarketing / retargeting shows ads to people who already visited or engaged and did not convert. In Nepal that is usually the Meta Pixel and Google Ads audiences sitting on the same landings used for prospecting. Arjan KC and Gurkha Technology run it as a stack technique, not a miracle cart-recovery product. Terms: retargeting · dynamic remarketing · consent mode · conversions API. Service page: Remarketing Nepal.

→ PPC Nepal · Conversion tracking · Case studies

Published results (and what is not published)

Numbered results on this site are Search / SEO / Maps, not a remarketing lift:

Those prove account structure, negatives, and tracking — the same discipline remarketing needs. An older e-commerce retargeting write-up on this blog is not a published sales-percentage case study. This page is the method. The featured image is reused from the media library, not as proof of that lift.

Retargeting creative for Nepal campaigns

Image: Arjan KC media library — retargeting creative, not a result claim.

Setup that actually runs

Piece Default Nepal failure mode
Pixel / tag Meta Pixel + Google tag on the landing, not only the homepage Tag on a desktop theme that mobile never loads
Audiences Site visitors 7/14/30 days; engaged social; video viewers One 180-day pool blasted with the same creative
Exclusions Purchasers, booked leads, staff IPs Paying twice for people who already WhatsApp’d
Creative Match the page they saw (SKU vs service vs clinic) Generic “we’re still here” with a different NPR price
Frequency cap Tight on Nepal CPMs; creative fatigue is fast Unlimited impressions until complaints
Conversion Purchase or documented proxy (chat, call, deposit) ROAS dashboards that ignore COD

Dynamic remarketing needs a product feed and a site that can take the click back to the same SKU. Many Nepal catalogs (especially marketplace-plus-WhatsApp) cannot support that feed honestly — use segmented static ads instead of fake “dynamic.”

COD, eSewa/Khalti, and WhatsApp

Cash on delivery and phone closes mean the browser conversion often never fires. Practice:

  • Fire events you can see: view content, add to cart, click-to-WhatsApp, submit form.
  • Import offline conversions when the CRM is real.
  • Report prospecting vs remarketing spend separately so a cheap remarketing CPC does not hide a broken Search CPA.
  • Do not tell a client the textbook “70% of carts recover.” Document the gap.

Festival spikes (Dashain catalogs, Tihar gifts) need shorter windows and fresh creative, not a larger retargeting pool of summer browsers.

Remarketing audiences are built from cookies and device signals, so they depend on what visitors allow. Google’s consent mode adjusts how Google tags behave based on the visitor’s choice in your cookie banner:

  • When a visitor accepts, tags set cookies and the visitor can join remarketing lists.
  • When a visitor declines, tags send limited signals without advertising cookies, and the visitor should not be added to remarketing lists.

Consent mode is required for traffic from the European Economic Area, which matters if you advertise to Nepalis in Europe or sell internationally. For Nepal-only sites it is still good practice: it keeps your tags honest about consent and gives Google modelled conversions instead of nothing when visitors decline. Expect remarketing lists to be smaller than total visitors once a banner is live, and plan budgets around that.

Customer Match: remarketing with your own lists

Customer Match lets you upload customer emails or phone numbers to Google Ads, which hashes them and matches them to signed-in users. Meta’s equivalent is custom audiences from a customer list. Uses that work in Nepal:

  • Exclude existing customers from prospecting, so you stop paying to acquire people you already have.
  • Win back past buyers with a new collection or service reminder.
  • Upsell customers who bought an entry product.
  • Seed lookalike audiences on Meta from your best customers.

Only upload contacts who gave permission for this kind of use, store phone numbers with the country code (+977) so they match, and refresh the lists regularly. Google sets eligibility requirements for Customer Match; check the current policy in your account. The first-party data guide covers collecting and cleaning these lists.

Meta audiences after Apple’s tracking prompt

Since Apple introduced App Tracking Transparency (ATT) in 2021, iPhone users choose whether apps can track them across other apps and websites. Many decline, so the Meta Pixel sees fewer iPhone visitors and conversions. In practice:

  • Website custom audiences are smaller than they used to be, especially for brands whose buyers use iPhones.
  • Conversion reporting is delayed and partly modelled.
  • Engagement audiences built inside Meta (people who watched your videos, messaged your Page, or interacted with your Instagram account) are unaffected by the website signal loss and often work better.

Set up the Conversions API alongside the Pixel so server-side events fill some gaps, and lean on engagement and customer-list audiences rather than only website visitors.

Frequency caps and creative rotation

Remarketing audiences are small, so the same people see your ads repeatedly. Too much frequency turns curiosity into irritation and comments like “stop showing me this”.

  • Google Display and YouTube: set frequency caps at the campaign level, for example a few impressions per user per day or week, and adjust based on results.
  • Meta: there is no simple cap for most objectives, so watch the frequency column and refresh creative when it climbs and results fall. Reach objectives allow frequency controls.
  • Rotate creative every few weeks: a reminder, a testimonial, an answer to a common objection, and an offer, rather than one ad on repeat.
  • Shorten windows for fast decisions (food, fashion) and lengthen them for slow ones (education, property, vehicles).

Hypothetical example: A Kathmandu furniture store retargets 30 days of website visitors with one sofa ad and sees frequency climb above ten per person with falling clicks. It splits the audience into 7-day and 8–30-day visitors, rotates three creatives, and excludes anyone who has already messaged on WhatsApp. Spend per enquiry drops and complaint comments stop.

Checklist

  • Google tag and Meta Pixel on every landing page, tested on mobile.
  • Cookie banner with consent mode, and expectations set that lists will be smaller.
  • Audiences split by recency and intent (product viewers, cart, chat starters).
  • Purchasers, booked leads, and existing customers excluded.
  • Customer Match and Meta customer lists uploaded only with consent, in +977 format.
  • Conversions API running alongside the Pixel.
  • Frequency caps on Google; frequency monitored on Meta.
  • Remarketing spend and results reported separately from prospecting.

Common mistakes

  • One giant 180-day audience with a single creative.
  • Not excluding people who already bought or booked.
  • Uploading contact lists collected without permission.
  • Judging remarketing on platform ROAS when sales close by COD or phone.
  • Ignoring consent and wondering why lists shrank.

Key takeaways

  • Remarketing works best on segmented, recent, high-intent audiences with matching creative.
  • Consent mode and ATT mean smaller website audiences; customer lists and engagement audiences fill the gap.
  • Exclusions save as much money as targeting.
  • Control frequency and rotate creative before fatigue sets in.
  • Measure with your own order and enquiry records, not only platform dashboards.

Where it sits on the stack

Useless without a conversion event (tracking). Align with SEM so brand searchers are not hammered by Display while they already type the name. IMC keeps the offer identical. Mobile landings: mobile marketing. Account work is described on the Google Ads expert and Meta ads expert pages.

Next: remarketing service page · Google Ads vs Meta · benchmark CPC tables.