Connecting advertising platforms
Meni.ge lets you link ad accounts to each location. The "Connected Platforms" block lives in the location card, in the "Marketing" section: open Locations, click the location you need and scroll its card down to "Marketing".
Linking is an "address book" of ad accounts: it records which advertising account a location works with, so managers don't have to look the ID up again and so advertising activity can be matched against the venue's performance.
Google Ads — Customer ID#
Format: XXX-XXX-XXXX (for example, 123-456-7890)
Where to find the Customer ID#
- Sign in to Google Ads
- In the top-right corner, next to the account name, the Customer ID is shown in the
XXX-XXX-XXXXformat - If you have multiple accounts, click the account icon and select the one you need
- Copy the ID (digits with hyphens, no spaces) and paste it into the Google Ads field in the Meni location settings
Manager account (MCC)#
If you use a Manager Account (MCC), each child account has its own Customer ID. Select the required client account in the left menu — the ID will appear at the top of the page.
Meta Ads — Ad Account ID#
Format: act_XXXXXXXXXX or a numeric ID (for example, act_123456789012)
Where to find the Ad Account ID#
- Open Meta Business Suite or Ads Manager
- In the left menu, select Ad Accounts
- Click the required account — the URL will include a parameter like
?act=XXXXXXXXXX - Or go to Business Settings → Ad Accounts — the numeric identifier is shown there
- Enter the ID in the
act_XXXXXXXXXXformat in the Meta Ads field in Meni
Personal vs business account#
- Personal ad account: the ID is visible in the Ads Manager URL
- Business ad account: configured in Business Manager → Business Settings → Ad Accounts
Yandex Direct — Client login#
Format: Yandex account login (for example, myrestaurant) or a numeric Client ID
Where to find the Client ID / login#
- Sign in to Yandex Direct
- In the top-right corner, your account login is displayed (for example,
myrestaurant@yandex.ru) - Use the login without @yandex.ru (only
myrestaurant) or go to Profile settings to view the numeric Client ID - If you are an agency, in the left menu (Clients) select the required client and copy their login or ID
- Paste the value into the Yandex Direct field in the Meni location settings
Agency access#
When switching to a client in an agency account, the URL looks like
direct.yandex.ru/...?ulogin=clientlogin. Use clientlogin as the identifier.
VK Ads — Ad account ID#
Format: numeric identifier (for example, 1234567)
Where to find the account ID#
- Sign in to VK Ads
- In the top-right corner, next to your name, the account number is displayed
- The ID is also visible in the URL:
ads.vk.com/...?account_id=XXXXXXX - Copy the numeric ID and paste it into the VK Ads field in Meni
Multiple accounts#
If you have multiple ad accounts (for example, via an agency), select the required one in the dropdown at the top of the page. Each account ID is unique.
myTarget — Client ID#
Format: numeric identifier (for example, 9876543)
Where to find the Client ID#
- Sign in to myTarget
- Go to Profile (user icon → Profile)
- In the Account section, the Client ID is shown — the numeric identifier of the ad account
- Or the ID is visible in the URL:
target.my.com/agency/clients/... - Copy the ID and paste it into the myTarget field in the Meni location settings
Agency account#
If you work through an agency account, go to the Clients section and copy the ID of the required client account.
Why this is needed#
| What linking an account provides | Description |
|---|---|
| Teamwork | Managers can see which ad account the location is using |
| Analytics | Matching advertising activity with restaurant performance metrics |
| Time savings | No need to look up the ID every time you set up campaigns |
There is no jump into the ad account itself from the location card: the field stores an account identifier, not a link.
Related articles#
- Analytics and tracking pixels — Google Analytics, Meta Pixel, Yandex Metrica
- Integrations — POS, delivery platforms, messengers, API