At a glance
| Field | Detail |
|---|---|
| What | Choose separate buyer and seller outcomes before selecting campaign goals. |
| Who it matters to | Acquisition teams promoting an app used by buyers and sellers. |
| Where | Google Ads App campaigns and TikTok app promotion; event options depend on integration and eligibility. |
| When it applies | When a shared signup goal would combine buyer and seller activity. |
| Action | Review event triggers, platform support and reporting before funding each goal. |
Marketplace app advertising starts with deciding which side needs an outcome. For an app used by buyers and sellers, we suggest defining buyer purchase and seller activation separately before choosing an optimization event. A shared signup event can record registration without establishing either outcome. The checks below apply Google Ads, TikTok and AppsFlyer documentation to that planning decision.
Define the outcome before the event name
AppsFlyer's ecommerce guidance distinguishes completed registration, initiated checkout, successful purchase and first purchase. Checkout starts before purchase is complete; first purchase is a separate suggested custom event. These definitions give buyer campaigns different milestones to measure. AppsFlyer's ecommerce event guidance supplies the triggers.
Our suggested seller milestone could be a first approved listing. That is a planning example; its availability as an optimization event needs verification. Write down the exact trigger and whether repeats count. For an app where an account can both buy and sell, identify the role through the action being measured rather than assuming signup identifies a permanent user type.
Separate goals without assuming separate audiences
Google recommends a new App campaign when optimizing for a different goal and warns that concurrent campaigns can compete for similar users. Its in-app-action guidance also says more frequent conversion actions provide more learning data. Google's goal-based setup guidance explains these tradeoffs.
Our interpretation: check each proposed action's availability and activity before creating separate buyer and seller campaigns. A campaign name does not establish a distinct audience. Review the immediate marketplace need before dividing budget, and keep the intended outcome in the brief. A buyer/seller budget allocation rule is not specified in the cited documentation.
Choose an event or a filtered conversion on TikTok
TikTok distinguishes advertiser-defined custom events from custom conversions that filter existing standard events. These are different ways to express an outcome, as its custom event and conversion comparison explains.
| Approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| Google Ads campaigns with different goals | Optimize separate App campaigns toward different goals | Concurrent campaigns can compete for similar users | Check each goal's event activity before splitting budget |
| TikTok custom event | Optimize toward an advertiser-defined in-app action | Requires TikTok SDK integration and custom-event eligibility | Verify that the intended seller milestone is selectable |
| TikTok custom conversion | Filter an existing standard event using parameters | Requires TikTok App Events SDK and supported filter fields | Verify the parameter's documented meaning and received values |
TikTok's custom-event documentation requires its App Events SDK, a valid SDK signal within the past 90 days, ad spend in the associated ad account every day for 9 days before starting the campaign, and at least 10 attributed events for the selected custom event within the past 9-day attribution window. These are requirements for custom event optimization.
Custom conversions also require TikTok's App Events SDK. Its customer_type filter documents new and returning customers; buyer and seller values are not specified in the cited documentation. Value optimization through custom conversions is limited to the upgraded Smart+ experience for app install and retargeting campaigns. Check the custom conversion documentation before assuming an analytics field or tracked event can become the desired bidding goal.
Keep the event definition intact in reporting
AppsFlyer describes events as names with optional parameters and recommends predefined names where possible to ease partner mapping. Custom events require developer maintenance. Its documentation also distinguishes lifetime-value event reporting from activity reporting for a selected date range. AppsFlyer's event overview explains these differences.
That overview says event parameter values appear exclusively in raw-data in-app event reports, and raw-data reporting is a premium feature. If buyer/seller separation exists only in a parameter, check reporting access before promising that split in an aggregate dashboard.
Our suggested review is to compare buyer and seller results on the same reporting basis and inspect whether each event definition survives mapping to the buying platform. If a seller milestone is unavailable for bidding, keep it visible in the business review and record that limitation. Use the measurement data-path review to align triggers, mapping and reporting definitions before comparing acquisition costs.
What to review
- Check whether buyer purchase and seller activation have distinct triggers, rather than sharing an undifferentiated registration count.
- Review Google's conversion-volume guidance for each proposed action before dividing campaigns.
- Confirm TikTok SDK integration, custom-event eligibility and event selection for the intended campaign.
- Check custom conversion fields against their documented meanings; distinguish new or returning customers from buyers or sellers.
- Compare results using the same outcome definition and reporting basis, and record unsupported seller goals explicitly.



