A healthy account stack is built with rules, not with hope. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. You want a procurement record that a new operator could understand without calling the person who bought the asset. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes.
Expect a workmanlike approach: selection criteria, handoff workflows, and measurement hygiene so your media buying machine stays stable under pressure. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing.
A selection framework for ad accounts that survives access, billing, and reporting changes (v4e)
If you operate Facebook Ads, Google Ads, and TikTok Ads in parallel, the ad account selection method must be repeatable. https://npprteam.shop/en/articles/accounts-review/a-guide-to-choosing-accounts-for-facebook-ads-google-ads-tiktok-ads-based-on-npprteamshop/ Treat it as your baseline: validate access, billing, and continuity controls before you tie the account to core budgets. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. You want a procurement record that a new operator could understand without calling the person who bought the asset. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent.
Set a weekly audit cadence and require at least 6 evidence items (screenshots, role exports, billing receipts) in your internal log. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing.
Buying with confidence: evaluate a TikTok verified TikTok Ads account like infrastructure
A TikTok verified TikTok Ads account is only useful if your team can control access and billing predictably. buy TikTok verified TikTok Ads account with reporting continuity in mind for small squads Look for evidence of stable permissions, a clean change log, and a conservative spend ramp rule for the first week. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked.
As an internal rule, don’t raise spend more than 25% per day until access, billing, and reporting have been stable for 4 consecutive days. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes.
TikTok TikTok Ads account due diligence: documents, permissions, and failure modes
If your team is under time pressure, a TikTok TikTok Ads account needs conservative guardrails from day one. TikTok TikTok Ads account with documented access history for mobile apps for sale Use buyer-oriented checks like role export evidence, billing responsibility notes, and a written recovery path before any ramp. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent.
As an internal rule, don’t raise spend more than 15% per day until access, billing, and reporting have been stable for 9 consecutive days. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly.
Creative ops without chaos: protect velocity with guardrails (scaling focus)
If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. You want a procurement record that a new operator could understand without calling the person who bought the asset. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent.
Decide what you will not do, then automate the rest
Example: a mobile app team documents roles and billing responsibility so a client handoff doesn’t turn into downtime. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion.
If it is not documented, it is not real—especially when multiple operators touch the same asset.
When is it smarter to pause scaling and fix the account layer? (scaling focus)
Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. You want a procurement record that a new operator could understand without calling the person who bought the asset. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. You want a procurement record that a new operator could understand without calling the person who bought the asset.
Define the access model before you define the budget
Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable.
| Check | What to look for | Evidence to store | Decision |
|---|---|---|---|
| Access roles | clear admin/operator split | role export + internal roster | proceed only if rotation is possible |
| Billing owner | documented payer responsibility | invoice/receipt + change log | avoid ambiguous payers |
| Recovery path | known recovery contacts/process | steps + timestamps | pause if recovery is unclear |
| Tracking baseline | events fire consistently | test log + screenshots | isolate if incomplete |
| Change management | one owner for edits | change log | escalate if multiple people edit |
| Creative QA | approval process defined | QA checklist | tighten claims before scaling |
| Reporting spec | metrics definitions stable | dashboard spec | lock spec before expanding team |
You want a procurement record that a new operator could understand without calling the person who bought the asset. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. You want a procurement record that a new operator could understand without calling the person who bought the asset. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. You want a procurement record that a new operator could understand without calling the person who bought the asset. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly.
Create a reporting baseline to detect drift early
Example: a mobile app team documents roles and billing responsibility so a client handoff doesn’t turn into downtime. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers.
Red-flag patterns buyers should learn to recognize early (scaling focus)
A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. You want a procurement record that a new operator could understand without calling the person who bought the asset. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly.
Treat billing as a governance control, not just a payment method
Example: a local services media buying team uses a scorecard to gate onboarding and avoids emergency resets during a seasonal push. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. You want a procurement record that a new operator could understand without calling the person who bought the asset. You want a procurement record that a new operator could understand without calling the person who bought the asset. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable.
Boring processes are a feature: they keep accounts stable when people and priorities change.
Which access mistakes cause the most downtime in the first two weeks? (scaling focus)
Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. You want a procurement record that a new operator could understand without calling the person who bought the asset. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly.
Keep a clean handoff log when multiple operators touch the asset
Example: a mobile app team documents roles and billing responsibility so a client handoff doesn’t turn into downtime. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes.
A procurement decision becomes an operations decision the moment spend starts.
Top mistakes buyers make — and the fixes that prevent repeats (scaling focus)
When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers.
Prefer boring workflows that survive staff changes
If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. You want a procurement record that a new operator could understand without calling the person who bought the asset. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent.
- Document creative QA rules that match your compliance tolerance.
- Verify a conservative spend ramp rule for the first week.
- Lock a reporting baseline with named metrics and definitions.
- Limit admin vs operator access for the TikTok TikTok Ads account.
- Document a reporting baseline with named metrics and definitions.
- Align a change log for credentials, roles, and payment method updates.
You want a procurement record that a new operator could understand without calling the person who bought the asset. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. You want a procurement record that a new operator could understand without calling the person who bought the asset.
Separate onboarding checks from optimization work
Example: a mobile app team documents roles and billing responsibility so a client handoff doesn’t turn into downtime. Avoid practices that misrepresent identity or ownership; keep your operations aligned with platform policies and applicable law. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies. You want a procurement record that a new operator could understand without calling the person who bought the asset. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week.
Governance and handoff: the part most teams underfund (scaling focus)
You want a procurement record that a new operator could understand without calling the person who bought the asset. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable.
Set up escalation paths before something breaks
Example: a local services media buying team uses a scorecard to gate onboarding and avoids emergency resets during a seasonal push. Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Keep your team’s behavior boring: consistent logins, consistent roles, and no shortcuts that look like evasion. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies.
Document ownership and roles like you would for a production system
Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers.
- Define a reporting baseline with named metrics and definitions.
- Confirm a “break-glass” recovery plan with timestamps.
- Confirm a conservative spend ramp rule for the first week.
- Document a cadence for weekly audits and monthly deep checks.
- Test a written onboarding checklist and sign-off owner.
- Verify admin vs operator access for the TikTok TikTok Ads account.
Prefer transparent, documented authorization over informal arrangements that collapse under review or dispute. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. When you touch policies, focus on prevention: minimize violations by controlling what you run, how you message, and how you track consent. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies.
Final operating rules that keep the account layer calm
Keep the workflow simple: one owner, one checklist, one evidence folder, and one escalation path. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. When multiple clients share attention, governance needs to be explicit, or every urgent request becomes a policy exception. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. If a platform’s terms restrict transfers, treat that as a risk variable and choose conservative operational boundaries. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. Start by writing down who needs admin-level control, who needs day-to-day access, and what you will do if that access is revoked unexpectedly. If you cannot explain how the asset will be managed in a month, you should not plan to scale it next week. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing.
Don’t confuse short-term deliverability with long-term stability; the latter comes from repeatable processes. Build guardrails that reduce the blast radius: separate test spend from core budgets until the asset proves stable. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Risk is rarely one thing; it is usually a pile-up of small ambiguities: unclear roles, undocumented billing, and ad hoc transfers. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. A stable asset has clear ownership, predictable permissions, and a path to rotate roles without breaking tracking or billing. The simplest way to prevent chaos is to enforce one naming convention, one handoff note, and one place where credentials are tracked. Treat every new asset as an onboarding project: collect evidence, store it, and only then attach campaign-critical dependencies.