NAMEOPS SUPPORT

Answers without ad-data exposure.

Start with the guidance below. If you still need help, contact us without attaching passwords, private rule URLs, customer lists, or raw advertising-account data.

Email support@wandrewlab.com
01

Install the extension

From the Chrome Web Store, choose Add to Chrome, then click the NameOps toolbar icon to open the side panel. For a local ZIP, unzip it first and use chrome://extensions → Developer mode → Load unpacked.

02

Choose Member or Local Administrator

Either role may optionally import a team pack during first-time setup. After setup, members can generate, validate, copy, fill, export, and refresh an already configured rule source, but only an unlocked local administrator can import or edit rules, configure sync, and change the Triple Whale setting.

03

Use another company’s rules

Import a complete standalone NameOps JSON bundle. It replaces the NameOps Starter values, including the Account prefix. Only a pack explicitly marked extends-nameops-starter inherits Starter values.

04

Connect an HTTPS rule source

A local administrator enters the HTTPS JSON URL and clicks Connect and Sync. Chrome asks for access to that exact origin. NameOps rejects embedded credentials, fragments, cross-origin redirects, responses over 2 MB, and reads longer than 15 seconds.

05

Separate Facebook and Instagram

When budget, objective, schedule, and optimization are shared, keep one Meta Campaign and use separate AUD + Placement Groups such as Instagram_Only and Facebook_Only. Different creative belongs at the Ad level.

06

Understand duplicate warnings

The duplicate notice only checks the latest history in this Chrome profile and matching local platform/account scope. It cannot guarantee team-wide uniqueness.

SAFE SUPPORT REQUEST

What to include

DO NOT SEND

Administrator passwords or hashes, private sync URLs, full destination URLs, customer data, live ad-account identifiers, or unredacted campaign exports.