Menu

One label, one campaign: splitting a store's Shopping ads by margin from the database
📰

One label, one campaign: splitting a store's Shopping ads by margin from the database

DEV Community: postgres·RAMO·3 days ago
#EVFD35Uv
#devtopostgresql#devto#dev#campaign#excluded
Reading 0:00
15s threshold

For a long time our Shopping setup on Google Ads was the default one: every product in the feed, one or two campaigns, let the bidding sort it out. On a hardware store that's a problem, because the catalog is wildly uneven. A tube of silicone sealant and a multi-part pipe fitting set have completely different margins, and a click costs roughly the same either way. Treating them as one pool means the cheap, thin-margin items quietly eat budget that should go to products that can actually pay for their clicks.

The fix everyone recommends is "split campaigns by margin using custom labels". That part is easy to say. The parts nobody writes down are where the label comes from, who's allowed to change it, and how you stop two campaigns from bidding on the same product. This is how we ended up doing it.

The label lives in the database, not in Merchant Center

Merchant Center lets you set custom_label_0 through feed rules or supplemental sheets. We tried a spreadsheet first.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.