Weekly eCommerce & Advertising Sync – Feed Policy Issues, Budget Shifts, Campaign Performance

Corporate Bookings / Overall Health

• Corporate-channel bookings remain stable.
  • Typical daily volume ≈ $20$ (no anomalies flagged).
  • No urgent risks detected on the B2B side.

eCommerce Feed & Policy Violations

• New Meta notification (arrived last night):
  • Product: “Cambrian Men’s Ultra Leather Shoe – Black.”
  • Flagged reason: Commerce Policy Violation (exact clause unclear).
• Ads are still delivering because Meta simply issues a warning and requests remediation; it does not auto-pause campaigns (unlike Google Ads, which can suspend delivery).
• Secondary Meta notice: “Add a backup payment method.”
  • Purely administrative; delivery continues while the team updates the billing profile.

Meta Commerce Manager vs Meta Ads

• Merchandise data (catalog, pricing, imagery, copy) lives in Commerce Manager, separated from the Ads interface.
• Violation resolution must occur inside Commerce Manager, not the Ads account.
• Analogy: Same workflow as the recent clean-up performed in Google Merchant Center.

Ownership & Access Issues

• Commerce Manager account cannot currently be located by the marketing lead.
  • Likely created by a former employee (similar to the prior Google My Business dilemma).
  • No single system of record has been maintained for platform log-ins, leading to:
  • Domains controlled by ex-staff.
  • A major sports-league client once lost its Facebook page for ≈3 months under similar circumstances.
• Action items:
  • Identify eCom lead or IT admin who connected BigCommerce → Meta.
  • Trace the unique Catalog ID from BigCommerce settings (API-driven “Connect to Facebook/Google” modules) to locate the Commerce account.
  • If the legacy account is irretrievable, create a fresh Commerce Manager instance and reconnect the feed.

Budget Reallocation & Campaign Adjustments

• Oakville Store Campaign paused.
• Re-allocated $1{,}000$ from Google P-Max to Meta.
  • P-Max daily budget dropped from $75\;/\text{day} \to \approx$42.
  • Target ROAS guidance edited to $1.13$ (was $1.28$).
• Geographic focus tightened to Ontario – Transactional Acquisition (best-performing segment).

Corporate Performance Metrics (Non-eCom)

• Running within the expected $80–120$ KPI range (exact metric unspecified; likely CPA or ROAS index).
• Holiday outlook: potential softening this week due to Canada Day seasonality.

Creative & Content Insights

• “New Orange” creative continues to outperform legacy assets in CTR and conversions.
• Nick supplied revised link parameters; boosted posts updated accordingly.
• Additional summer creatives just pushed live:
  • Sandals Asset Group.
  • 3 new Ad Groups focused on summer SKUs.
  • One-week performance data will be reviewed next Tuesday.

Canada Day Promotion

• Early indicators: strong engagement and sales lift.
• Consider extending the promo +1 week if inventory allows.
  • Aligns neatly with Amazon Prime Day (Tue-Wed next week).

Next-Step Checklist

1. Meta Commerce Manager
   • Locate/restore existing account OR spin up new catalog.
   • Remove/rename any SKUs that violate policy.
   • Confirm catalog sync cadence (daily feed push recommended).
2. Billing – Add backup payment method in Meta Business Settings.
3. Data Pulls – by next Tuesday:
   • Week-over-week performance for Sandals & Summer ad groups.
   • CTR, CPC, ROAS splits by creative (particularly “New Orange”).
4. Promotion Strategy
   • Decide by Tuesday whether to extend Canada Day sale through Sunday.
   • Prepare non-sale summer SKU push (targeting conversion rate gains).

Practical / Ethical Considerations

• Dependency risk: When individual employees control platform credentials, the business loses autonomy; implement an access-governance protocol:
  • Shared enterprise password vault.
  • Business-owned admin emails (not personal addresses).
  • Quarterly audit of platform roles.
• Compliance: Maintain parity between product copy/images and platform policies (e.g., age-appropriate imagery, no medical claims for orthotic shoes, etc.).

Numerical / Technical References

• Budget shift: $\Delta_{P\text{-}Max} = 75-42 \approx 33\;\$\text{/day}$ sent to Meta.
• Corporate KPI band: $80 \leq \text{Metric} \leq 120$.
• Target ROAS tweak: $\text{tROAS} = 1.13$.
• Sale lift example: $130 \to 170$ transactions ⇒ $\Delta = 40$ incremental sales at 40.40\$ \approx 1{,}616\$ revenue impact.

Key Platforms Mentioned & Roles

• Google Merchant Center – Feed governance (already cleaned up).
• Meta Commerce Manager – Current violation to fix.
• BigCommerce – Source of catalog; houses API keys/IDs for feed connections.
• Google P-Max & Meta Ads – Downstream ad engines pulling from above feeds.
• Google My Business / Facebook Page – Brand presence; must stay under company control.

Meeting Logistics & Follow-Ups

• Next sync: Tuesday (post 1-week data accrual for new summer campaigns).
• Stakeholders to invite: eCom lead (access ownership), finance (backup payment), creative (promo extension assets).