Uberall’s Social Ads solution empowers corporate and location-level teams to launch paid media campaigns at-scale. The solution can be tailored to your specific paid media objectives whether you are trying to generate awareness for a particular campaign or drive traffic to your locations.
The purpose of this guide is to outline the process for enabling the Social Ads solution in Uberall! The Uberall team will need to gather some initial information from you regarding your paid social strategy to ensure that we are configuring the solution appropriately for your specific needs. Additionally, there are a few required prerequisites before we can configure the social ads solution in Uberall.
Discovery Questions
- Do the locations fund all local campaigns, or are there instances of corporate-funded local campaigns?
- What are the business goals/objectives for local campaigns?
- Do you require approval before campaigns go live?
- Who are the users running campaigns today?
- What's the publishing frequency?
Note: Please provide answers to these questions above to your Implementation Consultant.
Social Ads Prerequisites:
- Meta Business Manager Access: Please add Uberall to your Meta Business Manager account. Provide william.sholan@uberall.com and laura@local-ads-support.com with Full control rights to your Meta Business Manager account. (This step is required to ensure that our social application can be configured in the Business Manager; The social application connects to any relevant Meta pages/ad accounts required for social ads publishing).
- Meta Ad Account Setup: If locations fund all local campaigns, please provide the ad account IDs associated with each participating location; If corporate funds local campaigns for specific locations, please specify which locations and please provide the corporate ad account ID. (Please provide this information to your Implementation Consultant)
Implementation Timeline
Our standard implementation timeline is based on the following client assumptions:
- The client has one Meta Business Manager account which houses all Meta pages & Ad accounts
- The client has obtained proper admin access to the Meta page(s) via the Business Manager account (only pages with proper admin permissions in the Business Manager can be used for Ads)
- The client has proper access to the Ad account(s) in the Business Manager (only ad accounts with proper access in the Business Manager can be used for Ads)
Note: Please reach out to your Implementation Consultant and/or CSM if you have any questions regarding these assumptions.
What to expect during the Implementation Process
Stage |
Activities |
Date |
Owner |
| Plan | Discovery Call to align on paid social strategy | Week 1 | Uberall / Client |
| Provide access to Meta Business Manager account | Week 1 | Client | |
| Share ad account IDs and associated locations to begin ad account location mapping | Week 2 | Client | |
| Confirm Approvals to enable moderation for campaign publishing | Week 2 | Client | |
| Build | Connect social application to Meta Business Manager account to facilitate platform connection to pages and ad accounts | Week 2 | Uberall |
| Connect locations to Meta ad accounts | Week 3 | Uberall | |
| Configure Approvals in platform | Week 3 | Uberall | |
| Create groups to enable targeted campaign publishing and report filtering | Week 4 | Uberall | |
| Confirm location ad account mapping | Week 4 | Client | |
| Campaign Configuration Training to review process to add and maintain Meta Ad Accounts (Corporate) | Week 5 | Uberall / Client | |
| Campaign Platform Training (Corporate) | Week 5 | Uberall / Client | |
| Launch | Enable social ads capability in platform and provision user access | Week 6 | Uberall |
| Create Social Ads templates in platform | Week 6 | Client | |
| Launch social ads campaigns in platform | Week 6 | Client |
TigerPistol (TP) and Uberall Platform Integration: Key Points
Regarding if Accounts, Groups, and Labels are moved into TigerPistol along with locations for campaign launches.
Syncing Groups/Labels to TP:
Uberall does not automatically sync groups/labels to TP.
Manual syncing is possible if required by the client.
Manual sync incurs 1 SP per 1 TP Account instance.
Multiple SPs result in multiple TP Accounts
Client Capabilities in TP:
Clients can create groups/filters within TigerPistol for segmented campaign publishing.
Prospect with Multiple Brands in Different Countries:
Each country would have a separate Service Point (SP).
TP would be set up with multiple instances corresponding to each SP.
Each SP allows access to individual campaigns and reporting only.
No overall global view in TP for the performance of all SPs.
Example: Little Caesars US and Little Caesars Canada have separate SPs and TP instances.
Super admin can access both SPs in Uberall but must log into each TP instance independently.