Meta Ads Assets Explained: A Step-by-Step Setup Guide

Before creating your first Meta campaign, connect the people, brand identities, ad account and business data that the campaign will use. This tutorial explains what each object does, how to configure it, and how to check that the connections actually work.

Follow the steps in order when setting up a new business. If you are taking over an existing account, inventory its owners and IDs first. Creating another Page, pixel or catalog often makes an access problem harder to solve.

About the screenshots: The interface examples below come from the tutorials supplied with the original guide; each image credits its source. They are not screenshots of your account. English labels and existing annotations are retained. Menus vary by region, eligibility and interface version; verify the object name, ID, owner and permissions in your own account.

Choose your setup path before creating assets. If you are taking over an existing account, inventory its owners, IDs and connections first. Website purchases, instant-form leads, messages and app promotion use different destinations; section 13 helps you identify the assets your campaign needs. You do not need every asset in this guide for every campaign.

1. Separate ownership, access, connections and data transmission

A personal login identifies the operator. A business portfolio organizes business assets and permissions. The Facebook Page and Instagram account provide the public brand identity. The ad account contains campaigns and billing. Datasets receive business events, while catalogs store product information.

Check each relationship separately. Agency access to an ad account does not automatically provide access to the Page, Instagram account, dataset or catalog needed for the same campaign.

2. Keep an inventory of the core assets

Business Suite, Ads Manager, Events Manager and Commerce Manager are working interfaces, not interchangeable account types. Use business settings for access, Ads Manager for campaigns, Events Manager for event diagnostics, and Commerce Manager for catalogs and commerce features.

3. Secure individual logins before adding assets

1. Use each operator’s own authorized login. Check recovery email and phone details, enable two-factor authentication, and keep recovery information secure.
2. Open the business tools and confirm the selected portfolio before creating anything. If your organization uses managed Meta accounts, follow its work-account process.
3. Accept the business invitation, then verify that the required assets are actually visible. A successful login does not mean asset access is complete.
4. Keep reliable administrative coverage. As an operational precaution, appoint at least two trusted current staff members who can independently sign in and manage the business.

Do not hand over a personal Facebook account when an employee leaves. Reassign business permissions instead. Shared passwords, rented portfolios and purchased accounts create ownership and recovery problems.

4. Create or verify the business portfolio

1. Check whether the business already has a portfolio. Obtain authorized access to that portfolio before deciding to create another.
2. When a new portfolio is needed, enter the real business name, responsible person and business email in Business Suite; complete the confirmation requested by Meta.
3. Open Business portfolio info or Business info. Record the portfolio ID and check the business details.
4. Review full-control access and security settings, then add the assets the business should own. Complete business verification when required for the relevant feature or account.

A portfolio ID, Page ID, ad account ID and pixel ID identify different objects even when they all look like long numbers. Providing an agency with a portfolio ID does not itself grant access.

5. Connect the Facebook Page and Instagram identity

1. Create or identify the brand’s Facebook Page. Check its owner and your Page access before creating a duplicate.
2. Use an appropriate Instagram professional account type. A business account is a common choice for a brand; choose according to the available features and business needs.
3. Connect the Page and Instagram account through the relevant linked-account settings. Then check both objects under Pages, Instagram accounts or Business assets.
4. Assign the necessary Page and Instagram tasks to people or partners, and complete any required ad-account connection.
5. In an ad draft, select the intended Page and Instagram identity and inspect the preview.

Linking the identities, adding them to a portfolio, and allowing a person or ad account to use them solve different problems. Some advertising flows support other identity options; this is the usual configuration for a brand managing both channels.

6. Set up the ad account and billing

1. In business settings, open Accounts → Ad accounts or the equivalent asset entry. Record the account ID and owner.
2. Confirm currency and time zone before creation. They affect billing and reporting; changes can have account-level consequences rather than behaving like a simple profile edit.
3. In Billing and payments, add a supported payment method and the appropriate billing and tax details. Confirm who is responsible for payment.
4. Assign operators, set appropriate spending controls, and review account status. Payment methods and account limits depend on the region and account.

Selling in several countries does not automatically require one ad account per country. Design the structure around billing entities, currencies and operational needs. Ownership changes, removals and transfers have asset-specific restrictions; check before claiming an account.

7. Grant people and agencies the access they need

Permissions have two layers: portfolio access and tasks on each individual asset. After inviting a person, assign the actual Page, ad account, dataset or catalog they need.

1. Under People, invite the colleague with the appropriate portfolio access level.
2. Select the assets and task permissions, then have the colleague accept.
3. Ask them to perform their actual work using their own login. Review access again after role changes.

Connect an agency as a partner

1. Confirm the brand’s and agency’s portfolio IDs through the agreed contacts.
2. Use Partners to share selected assets, or review and approve the agency’s access request.
3. Grant the required ad account, Page, Instagram, dataset and catalog tasks individually.
4. Have the agency test the advertising identity, optimization event and catalog.
5. When the engagement ends, review active ads, billing, integrations and credentials before removing the former access.

An agency normally assigns its own employees after receiving partner access. The brand does not need to share its Facebook password. Partner access grants usage rights; it is not an ownership transfer.

8. Connect the dataset and pixel to your website

1. In Events Manager or Data sources, identify any existing dataset or pixel. Verify its ID and owner.
2. If a new source is needed, follow Connect data → Web or the available dataset flow. Some pixel-to-dataset transitions retain the ID, but not every dataset is simply a website pixel.
3. Choose one primary integration: an official commerce channel, a supported partner, or a maintained custom installation. Audit themes, tag managers, apps and old plugins for duplicate tracking.
4. Configure the relevant business events and give the intended ad account access to the dataset.
5. Run a controlled user journey, then confirm the dataset and optimization event can be selected in the campaign configuration.

PageView only confirms that a page event arrived. It does not validate purchases, lead submissions, amounts or currencies. Pixel Helper mainly inspects the browser side and cannot independently confirm server-side CAPI delivery.

9. Choose a Conversions API implementation

Send events to the correct dataset and assign a maintainer. Direct integrations must follow the current event specification, including event name, time, source, business parameters and permitted matching fields. Keep access tokens server-side or in a secrets manager. A partner integration does not necessarily require you to create your own app or system user.

CAPI complements browser collection; it does not remove the need to handle consent and user choices. Plan deduplication whenever both paths report the same action.

10. Follow the right setup path for your store

Shopify: use the official Facebook & Instagram channel

1. Check the channel requirements: the connecting Facebook user needs full control of the relevant portfolio and Page, and the selected portfolio must own that Page. The Page must be published. The store must not be private and must have a valid sender email. Other connected assets also need the required permissions.
2. Before enabling another connection, review existing theme code, custom pixels, tag-manager tags and apps. Identify which installation sends each event so that the new connection does not introduce duplicate senders.
3. Install or open Facebook & Instagram by Meta. Verify the selected portfolio, Page, Instagram account, ad account, dataset/pixel and catalog by ID.
4. In Shopify, open Sales channels → Facebook & Instagram → Settings → Data sharing settings. Enable Customer data sharing and choose the appropriate level for your data-processing arrangements. If no Pixel is connected, select the intended existing Pixel and click Connect or Confirm, as shown in your interface.
5. Compare the connected Pixel ID with your asset register. Save, reopen the settings to confirm the connection, then run the controlled order test in section 11.

If another employee can see the channel but it appears disconnected, check that employee’s authorization first. Shopify requires staff who use this channel to connect their own Facebook account with full control of the associated portfolio and Page. This channel requirement does not mean every advertiser or agency needs full control of all business assets.

For ownership and connection prerequisites, review Shopify’s channel setup instructions.

Enhanced already includes CAPI. Do not assume that only Maximum supports it. Check Shopify’s data-sharing documentation for your channel’s options. If you also configure Shops, review its eligibility and verified-domain requirements; current Shopify guidance directs shoppers to your website to complete checkout.

Custom sites and other platforms

Use a supported, maintained integration or let the development team own the event definitions, destination IDs and deduplication rules. For WooCommerce, check the current Meta-published integration before installing another tracking plugin. Follow the platform’s supported event behavior rather than rewriting it simply to match a generic checklist.

11. Define and test the events that matter

Deduplicate the same browser and server action

For an illustrative order O1042, the browser sends Purchase with eventID=order_O1042 and the server sends Purchase with event_id=order_O1042. Both go to the correct same destination. Use the same event name and matching event identifier for that action; do not reuse the identifier for different orders or actions.

Browser: Purchase | eventID = order_O1042
Server:  Purchase | event_id = order_O1042
Product: content_ids = ["sku_blue_m"]

event_id identifies the action; content_ids identifies the products. An email address, an order_id field alone or an Event Match Quality score does not replace correctly implemented deduplication. Check the Meta deduplication specification when building a direct integration.

1. Use Test events to follow a product view, cart addition, checkout and controlled order. Inspect available Browser and Server parameters.
2. Some partner integrations do not expose server events in the test panel. Also inspect normal event activity, integration diagnostics and deduplication information.
3. Review Diagnostics, coverage, matching quality and freshness. Event Match Quality measures matching information, not order accuracy, deduplication rate or ROAS.
4. Compare the order, amount, currency and items with the store backend. Events Manager reception and Ads Manager attributed results have different reporting scopes.

Follow one order from the store to Meta

Record the integration, destination ID, test time and time zone, consent state, order reference and purchased variant. Define the expected Purchase value using your integration’s documented rules before comparing amounts. Shopify describes order-value events using the order’s total price, including duties, taxes and discounts; do not substitute net product revenue without checking the definition. See Shopify’s event definitions.

Use the following worksheet for a real controlled order. Record observed evidence and mark unavailable checks as “Not verified”.

An event arriving in Events Manager confirms receipt, not that Ads Manager will attribute a sale to an ad. If your integration does not expose an identifier or server event in Test events, record the limitation and use available event activity and integration diagnostics. Do not mark an unseen check as passed.

12. Build the catalog and connect product events

1. In Commerce Manager, create or identify the catalog and verify the owner. Reuse the intended platform-synced catalog where appropriate.
2. Choose the primary product source: platform sync, a supported data-feed file or another available method. Assign the refresh frequency and maintainer.
3. Check item IDs, titles, images, prices, availability and destination URLs. Sample variants and out-of-stock products.
4. Create product sets for the subsets you want to advertise, and assign the required people and ad-account access.
5. Connect the correct event source when product-event matching is needed. Then inspect a real item’s complete ID in both the catalog and event.

The catalog describes what you sell; events describe what people do with those products. If a catalog uses sku_blue_m and the event sends unrelated ID 1042, matching can fail. Check prefixes, capitalization, variant versus group level, and the integration’s content_type convention before changing IDs.

A catalog does not automatically enable a Shop. Shopify’s Facebook and Instagram features share a product catalog; make product changes in the primary platform source and check channel availability, because manual Meta-side edits can be overwritten by synchronization. After a repair, check feed updates, event activity and matching again.

13. Confirm which assets your campaign actually needs

Not every Meta ad requires a website pixel and catalog. Configure the assets for your actual conversion destination rather than treating the entire inventory as a universal prerequisite.

For catalog advertising, verify the catalog and product set in the current creation flow. Custom Audiences define who may be reached; custom conversions define results from received events and rules. Lookalikes depend on an eligible source. In automated audience setups, confirm whether an input is a restriction or a suggestion.

Continue with the Meta Ads beginner tutorial once these checks pass. Its core sequence is to choose the business objective, configure conversion and audience settings, prepare the ad, inspect the preview and then monitor delivery. For channel roles, budgets and testing, use the full-funnel advertising planning tutorial.

14. Verify domains and maintain account security

When required for your chosen feature, open Domains under the relevant business settings and follow an available verification method, such as DNS TXT, an HTML file or a meta tag. Confirm the verified domain and owner. Domain control, business verification and a verification badge establish different things; none is equivalent to ad approval.

Domain verification is not a universal prerequisite for every ad. Shopify’s Shops requirements include products purchasable directly from a verified domain. Do not copy an old checklist that requires manually prioritizing eight web events for every current website campaign.

1. Require appropriate two-factor authentication and keep recovery methods current.
2. Maintain reliable administrator access while giving daily operators only their required tasks.
3. Periodically review People, Partners, System users, connected apps and payment details. Remove expired access.
4. If delivery is restricted, identify the specific affected person or asset in Business Support Home or the relevant status screen before attempting a repair.

15. Add advanced integrations only when the business needs them

For a direct API integration, an app identifies the application, a system user provides a machine identity, and an access token authorizes calls. Verify the app permissions and asset assignments together. Record the app ID, maintainer, allowed assets, credential location and rotation process; do not paste plaintext tokens into the ordinary asset register.

For WhatsApp, distinguish the business account from its phone number. Check the display name, connection method and message-handling arrangement. The Business App and Business Platform have different workflows; number migration and coexistence depend on the current supported process.

For leads, decide how the CRM will return quality and sales outcomes. For apps or offline transactions, choose an appropriate SDK, API or partner connection. Define the business outcome and maintenance responsibility first, rather than adding every integration before launch.

16. Run a launch test and prepare the handover

Maintain one shared asset register

Use these columns in your spreadsheet: asset type, name, ID, owner, responsible person, people permissions, partner permissions, connected asset IDs, integration method, last test date, issue and issue owner. Store technical secrets separately.

An illustrative row might describe Brand_Main_USD as the brand-owned ad account, connected to Dataset_Web and Catalog_Store, with campaign access for the buyer and billing access for finance. Replace example names with real IDs and explicitly mark shared assets.

Before changing agencies, review live campaigns, automated rules, budgets, unpaid invoices and platform sync. Confirm the new team can operate the setup, remove former access as agreed, review apps and tokens, and repeat the identity, event and catalog tests.

17. Troubleshoot the missing relationship first

Record the current IDs and connections before making a change. Fix one identified issue at a time, keep a change log, and repeat the same test journey. This gives you a usable advertising setup and a record the next operator can understand.