Setting up Marketing integrations for multi-stores

What is a multi-store setup?

• Lifetimely supports multiple Shopify stores under one multi‑store account—each store, however, requires its own subscription. Make sure you're set up for multi‑store access (red here).
• Once connected, you can easily toggle between stores or view aggregate (“Consolidated view”) metrics using the Store dropdown in the dashboard (read here).

What's the problem?

It is common for multi-store users of Lifetimely to use one marketing account (be it Facebook Ads, Google Ads, or TikTok ads) for all of their stores.

For example, let's consider a setup where a merchant has a UK store, a DE store, and a FR store but uses a single Facebook Ads or Google Ads account.

If this single Facebook ads or Google ads account is connected to each Lifetimely account (please note that a Lifetimely account can only be connected to one Shopify store at a time), then there is a possibility that the spending data meant for DE store syncs to the UK Lifetimely account's marketing spending which inflates the costs and reduces the profits.

But no worries, Lifetimely has a solution to this conundrum.

The setup to solve this:

In each Lifetimely account, when you go to the respective marketing integration from the page https://lifetimely.useamp.com/integrations, there is an option to exclude the spending data from campaigns that are not relevant to the current store.

Here's a screenshot of this option that you see under each marketing integration:

In the text field, you need to enter the exact keyword that is present in your campaign(s). For example, if you enter the keyword "DE", then all the campaigns that have the keyword "DE" in their name will be excluded from Lifetimely.

So, you can use this trick in your UK account to exclude the campaigns that are meant for DE and FR stores. This way, the ad spending data will be accurate in each of your Lifetimely accounts,

Note: In the case of Facebook Ads, though, when you filter campaigns, please note that the data is delayed by 24 hours.

Here are the steps:

Also, use UTM Parameters to Attribute Campaigns to Specific Stores

Since you have one ad account managing campaigns across multiple stores, the best way to differentiate performance by store is through UTM tagging:

• In your ad campaigns, append UTMs that specify the store—for example:
  • ?...utm_source=google&utm_medium=cpc&utm_campaign=UK_store_campaign
  • ?...utm_source=google&utm_medium=cpc&utm_campaign=DE_store_campaign

This will let Lifetimely assign resulting revenue to the correct store using its UTM Explorer, which ties Shopify order data to those UTMs (first-touch or last-touch) (read here).

Then, drill down and analyze Ad Spend & Revenue by Store

Once your tagging and integrations are in place:

• Use Attribution → Overview to see overall campaign performance by channel (Google, Facebook, TikTok) across stores (read here).
• Use the Drill Down report to get granular: campaign → ad group → ad-level performance per store (read here).
• Use UTM Explorer to visualize revenue, ROAS, conversions, and orders tied to your store-specific UTM tags (read here).

Combine the above with store selection in the dashboard to view metrics per store or aggregated.

Important notes to consider:

• Currency Conversions: Lifetimely automatically converts ad spend into your Shopify store's currency, so ensure you're mindful of this when looking at spend vs. revenue in different currencies (read here).
• Time Zone Differences: If your stores operate in different time zones, the consolidated totals may not exactly match the sum of individual store metrics due to conversion timing and order assignment differences (read here).

To conclude, by connecting your stores correctly, using store‑specific UTMs, and leveraging Lifetimely's attribution reports, you’ll be able to clearly split ad spend, revenue, and ROAS per store—even when all campaigns run from a single ad account.

If you'd like help designing naming conventions for UTMs or navigating Lifetimely dashboards, our support team would be happy to assist further!