A Structure Map for Continuity: Recording Accounts, Owners and Payment Instruments

Editorial team Spend Ledger

Why a structure map matters

A growing advertising program can become difficult to oversee even when every account has a clear purpose. A business may operate several ad accounts, use different payment instruments, assign work to an internal team or agency, and connect tracking assets to campaigns. If those relationships are recorded only in individual inboxes or remembered by particular staff, routine changes can create avoidable confusion.

A structure map is a concise operational record of how the program is arranged. It shows which accounts exist, which business owns each one, who administers it, how its advertising is funded, which tracking assets are connected, and where recovery contacts can be found. It is not a method for concealing relationships or working around platform checks. Its purpose is to make legitimate ownership and responsibility easier to understand.

A well-maintained map helps the business identify who can make changes, who should be contacted when access is interrupted, and which assets might be affected by a change in ownership, billing or staffing. It can also support informed conversations with an agency or internal finance team. The document should describe the actual arrangement, not an intended arrangement that has not yet been put in place.

Set the scope before recording details

Start by deciding what the map covers. For some businesses, it will describe one legal entity and the advertising accounts it owns. For a group with multiple operating businesses, it may need to show each entity and the accounts associated with it. Keep the scope broad enough to reflect real dependencies, but not so broad that the document turns into a directory of every campaign setting.

Use consistent labels for accounts and business entities. These labels should be recognizable to the people who need the map, while avoiding unnecessary sensitive information. Record the platform and account identifier where appropriate, but do not include passwords, authentication codes, full payment card details, identity documents or other credentials. A map should help authorized staff locate the right record, not become a store of secrets.

Include accounts that are active, paused or retained for a legitimate operational reason if they remain part of the business’s structure. Mark their status plainly. If an account has been closed or is no longer controlled by the business, record that status according to the organization’s retention practices rather than leaving it presented as active. Do not list an account as belonging to a business merely because someone can access it; ownership and access are different facts.

Record ownership, administration and responsibility

For each account, identify the business that owns or is responsible for it. Where the arrangement is more complex, explain the relationship in plain language. For example, an agency may administer an account for a client, while the client remains the owner. The map should not blur those roles. If ownership or control is unclear, treat that as an issue to resolve through the relevant agreement and platform records, not as a detail to guess.

Next, record who administers the account. This may be an internal team, a designated role or an external service provider. Prefer role-based descriptions where practical, because staff members and contractors can change. Record the appropriate contact route for the responsible role, but keep access credentials and recovery secrets in approved secure systems.

It is useful to distinguish between the person or team that can manage settings and the person accountable for business decisions. The administrator may handle routine access and configuration, while a business owner or finance lead approves changes to funding or ownership. If more than one party has access, the map should make the arrangement understandable without implying that every listed party has equal authority.

When an agency is involved, the map should reflect the written working arrangement: which party owns the account, which party administers it, what happens when the engagement ends, and how access and records are handled. Avoid relying on informal assumptions. If the documented arrangement and the actual account setup do not match, flag the difference for review.

Connect payment instruments carefully

The funding section should show which payment instrument is associated with each account and which business is responsible for it. Use a non-sensitive label, such as an internal finance reference or a description that lets authorized staff identify the instrument without exposing its complete details. Do not copy full card numbers, bank credentials or security codes into the map.

Record the responsible finance contact or team and note any relevant billing arrangement, such as whether the instrument belongs to the account-owning business or is provided under an agreed agency arrangement. Keep the distinction between the payment instrument’s holder, the party billed and the party responsible for approving spend clear. These roles may not be identical.

The map should also show where staff can verify current billing information through the appropriate official account records. Do not treat a spreadsheet as the authoritative source for live payment status. Billing arrangements can change, and the platform’s account and policy pages are the place to check current requirements, accepted methods and any applicable restrictions.

If an instrument is replaced, expires, is removed or is no longer authorized for use, update the map after the change has been confirmed. Do not use a different instrument or account to get around a payment restriction, review or other platform decision. Investigate the cause through the platform’s official support channels and correct the underlying billing or authorization issue.

Map tracking assets and dependencies

An account map is more useful when it records the tracking assets connected to advertising activity. Depending on the business’s setup, these may include measurement properties, conversion events, audiences, product feeds or other business assets. The goal is to make dependencies visible: which account uses an asset, which business controls it, and who is responsible for maintaining it.

Use the asset’s recognizable name or internal reference, together with its owner and administrator. Record the relationship, rather than duplicating configuration details that belong in a separate technical inventory. If an asset is shared across accounts or business units, state that clearly and identify the party responsible for approving changes. Shared assets can create operational consequences beyond a single ad account, so their dependencies should not be left implicit.

Limit the map to information needed for coordination. It should not contain customer-level data, access tokens, private keys or implementation secrets. If staff need technical instructions, point them to the organization’s approved documentation location. Keep the map readable for business, finance and operations teams, not just for the person who set up tracking.

Put recovery contacts in the right place

Recovery information is essential to continuity, but it must be handled with care. The map should identify the role or team responsible for account recovery and indicate where the current, approved recovery procedure is documented. It can include business contact routes that staff are authorized to use, but it should not contain passwords, one-time codes, backup codes or personal identity records.

Record which business contact is responsible for receiving platform notices and who can coordinate with the account owner, administrator and finance team. Where recovery depends on a staff member or agency contact, identify a suitable role-based backup so the process does not depend on one person being available. Keep contact details current and ensure that the people listed have agreed to the responsibility.

If access is lost, follow the platform’s official recovery and appeal routes. The map can help establish who owns the account and where relevant records sit; it cannot substitute for the platform’s verification process. Do not create replacement accounts to bypass a restriction, obscure a relationship or avoid a review. Preserve relevant records and address the stated cause through the appropriate official channel.

Keep the map current and controlled

Update the map whenever a material relationship changes: an account is created or closed, ownership changes, an administrator is added or removed, a payment arrangement changes, a tracking asset is connected or retired, or a recovery contact changes. A change should be recorded when it is confirmed, not left until someone happens to review the document.

Alongside event-based updates, assign a regular review cadence that fits the pace and complexity of the program. The review should confirm that listed accounts still exist, owners and administrators remain accurate, payment references still point to authorized arrangements, and tracking and recovery details are usable. The business should choose the cadence internally; current platform-specific requirements should be checked on the platforms’ official help and policy pages.

Give one role responsibility for maintaining the map and another appropriate role responsibility for reviewing it. This separation can help catch omissions, particularly where account access, billing and business ownership sit with different teams. Store the document in an approved location with access limited to people who need it. Keep a record of revisions if that supports the organization’s governance, and remove outdated copies from places where staff might mistake them for current information.

Make the map useful to its readers

Different readers need different information. Operations staff need to understand account relationships and dependencies. Finance needs to identify who funds each account and who approves billing changes. Business owners need to see which entity is responsible. Agency contacts need clarity about the authority and access granted to them. Recovery contacts need to know where to begin if access or account status becomes an issue.

A one-page view should prioritize relationships, not every detail. A compact table can include the account reference, status, owning business, administrator, payment reference, connected tracking assets, and recovery contact or procedure location. Use a brief note for exceptions or shared arrangements. If the map becomes too dense, keep the overview to one page and maintain supporting records separately, with clear references to their approved locations.

The finished document is a practical control, not a guarantee of uninterrupted access or platform approval. Its value comes from being accurate, secure and understood by the people who rely on it. When ownership, funding or access is uncertain, record the uncertainty and assign it for resolution rather than filling the gap with an assumption.