Sponsored Content Revenue Log: A Record Layout

A publisher can follow the first few sponsored posts from memory. Once the count grows, recalling which piece ran when, for whom and under which label becomes hard. A sponsored content revenue log is a plain table that keeps those facts together. This article covers which fields the log needs, how to separate line items, how to carry disclosure and rel details, why tax questions go to an accountant and how to review the log over time. It contains no earnings figure, revenue expectation, commission or payment timing; for Akua publisher terms the only reference is the pricing policy page on the site. Every value in the table is hypothetical, and nothing here is legal or financial advice.

Why a Sponsored Content Revenue Log Is Kept Apart From Ad Revenue

Ad revenue is usually a repeating stream collected automatically. A sponsored piece is a separate agreement with its own text and its own label. Putting both on one row erases the context of each sponsored piece. A broader guide to the income types a site can have, the overview of website revenue models, shows the contrast from another angle; this article stays with the record.

One agreement per row, not a stream

A single row of an impression stream can summarize thousands of views. In sponsored content every row describes one publication: who asked for it, what ran, on what date, under which label. That difference in unit makes it awkward to fit both incomes in the same table.

Label and responsibility live only here

In an ad stream, the notice shown to readers is often managed by the network. In sponsored content, the label and the link attribute are the publisher's own decisions, and the trace of those decisions belongs in the sponsored record alone.

What separation costs and what it earns

A separate log takes some effort. In return, a year later the question "was this piece sponsored and did it carry a label?" is answered at a glance. The layout described here does not estimate income; it only keeps records.

Record Fields: Date, Party, Content, Label and Status

The spine of the table is five fields. A site owner who sells placements on their own pages is the subject of this piece written from the seller's seat, and the record fields are the readable aftermath of that role.

Date: one column will not do

The first field is date, but a single column falls short. The date a request arrived, the date it was approved, the date it ran and the date it closed each get their own column. The fifth section below looks at these four in detail.

Party: for whom and through which channel

In the party column, write the name of the person or company and the channel the request came through. Do not gather more personal data than you need; enough to continue the relationship is enough. In a hypothetical entry, "Company A, via the form" will do.

Content, label and status columns

The content column holds the page address and a short title. The label column carries the wording shown to readers and the link's rel value. The status column draws from a short fixed list such as draft, approved, published, disputed, closed. Fixed values make filtering easy later, which free text never does.

Separating Revenue Line Items by Type

Not every sponsored job is the same kind of work. Splitting line items by type gives clarity in the log and in later reviews. Ad revenue measures have their own explanation in the article on per-impression publisher metrics, but those are per-impression measures and do not belong here, since this log runs per piece of content.

Line item types: article, link, space, package

A sponsored article, a link added to an existing piece, a reserved ad space and a package covering several pieces are the four basic types. Each needs different information: a package needs the number of pieces it covers, a space needs position and duration.

Filtering by the type column

The type column should be a pick list. In a hypothetical case, at year end you want to look only at "article" items; the type column narrows the list without hand sorting. It is the most used filter in the table.

An interim value for unclear types

If you cannot tell which type a job is, use the value "unclassified" and write the reason in the note. Forcing it into a type makes you forget to fix it later.

Disclosure and Rel Label Details in Every Record

A record of a sponsored piece that does not say how the piece was marked is incomplete. The ethics behind labelling are argued at length in the guide to telling readers a post is paid for, and they reduce to two items on each row.

The disclosure readers see

Google's publisher guidance for news surfaces expects sponsorship to be stated clearly and paid material not to overshadow the content. In the record, write the wording and position of the disclosure. A hypothetical entry: "at the top of the piece, under the headline, the phrase 'sponsored content'".

Which rel value the row should show

Google's outbound link documentation names sponsored for advertising or paid placements, with nofollow accepted where other values do not fit. The record should show sponsored as the default, and any exception should carry a reason. The spam policies state that paid links are not a violation when qualified with one of these values.

Confirming that the label is live

The record is a trace of what happened, not of what was intended. After publication, open the page, check that the label and rel value are visible and write down the date of the check. If the "verified" column is empty, that row is still an assumption.

Tracking Order, Approval, Publication and Delivery Dates

Four dates tell the life story of a piece. Knowing how long each stage took helps you plan later work. Expectations about how long a paid article takes and how revisions work are framed in a separate piece on timing, and the log stores how those expectations played out.

Four date columns

Request date, approval date, publication date, and delivery notice or closing date. On a platform such as Akua the order flow runs through selection, payment, seller acceptance, delivery notice and dispute, and mapping the dates in your own table to those stages makes the work easier.

An empty date is also information

A row with a publication date but no delivery date is a pending job. Do not force empty cells to be filled; filter them and review them at regular intervals.

Date format and time zone

Write all dates in one format. Using day-month-year in one column and month-day-year in another leads to sorting mistakes. Choose a single time zone and state it at the top of the table.

Adding Dispute and Correction Requests to the Record

Not every job closes smoothly. A correction request, a dispute or a withdrawal should be tracked in its own part of the record.

A correction request as a sub-row

When a correction arrives, do not overwrite the existing row; add a new sub-row beneath it. Write the date of the request, what was asked and the reply you gave. That way the first version and the latest version can be read side by side.

The record flow when a dispute is opened

When a dispute is opened on a platform, the status column changes to "disputed". The date, the reason and the outcome go in separate fields. If the outcome is not known yet, leave the field blank rather than writing a guess.

Writing down why a row closed

When you close each row, add a one-sentence reason: "delivered", "withdrawn", "closed after correction". At the end of the year the reason field shows which kinds of job produced trouble.

Sending Tax and Business Setup Questions to an Accountant

This article gives no advice on taxes or on business status. The log makes talking to an accountant easier; the accountant makes the decisions.

Questions to take to the accountant

How income is declared, whether the activity counts as a business, how invoicing should work and what applies when working with foreign parties are questions to carry to an accountant in a written list. The list should hold questions specific to your situation, not answers borrowed from this text.

What moves from the log to the accountant

An accountant usually asks for date, party, line item type and amount. You can export those columns from your log. Disclosure and rel columns are not needed for bookkeeping, so they can stay behind when exporting.

What this article does not say

How any income is taxed, which document should be issued, or whether a log satisfies a legal duty are outside its scope. Those matters are settled with an accountant or another qualified adviser according to your circumstances.

Comparing the Revenue Log With the Editorial Calendar

Read side by side, the sponsored log and the editorial calendar reveal the balance of the site. The principles for accepting outside content are set down when a site writes its guest contribution policy, which defines what the comparison rests on.

A visibility check, not a ratio

The aim is not to cap the share of sponsored content but to keep it easy for a reader to tell whether what they are reading is sponsored. If every piece in a month is sponsored, that month had no editorial content, and readers may notice.

A monthly side-by-side look

At month end, set the published rows in the log next to the rows in the editorial calendar. Note sponsored pieces that arrived back to back on the same topic and any editorial gaps. The notes feed into the next month's plan.

A decision rule for clashes

If a sponsored and an editorial piece collide on the same topic, tie the question of which one takes priority to a written rule. Without a rule, the decision follows the mood of the day and the record turns inconsistent.

Privacy and Access Limits of the Log

A revenue log carries traces of business relationships and sometimes of personal details. Who can open it, where it is stored and how long it is kept should be written down. A look at how terms are recorded can start from a checklist for contracts on advertising placements, which suggests which agreement details the log may need.

Access: who needs which column

Not everyone working with the log needs every column. Only an authorised person might see the amount column, while the editorial team sees content and label columns. A short list of sharing permissions is enough.

A minimum of personal data

In the party column keep only what allows the relationship to continue. If no identity number or sensitive detail is needed, do not enter it. A design that can later honour a person's deletion request should be planned from the start.

Backups and versions

Do not keep the table as a single copy. A regular backup makes an accidental deletion reversible. Note at the top of the table where the backup sits and who can open it.

Reviewing the Log Once a Year

An annual review questions the table itself: are the fields still useful, are some columns never filled, are the status values enough?

Pruning columns nobody uses

A column that stayed empty for a year is either unnecessary or one you do not know how to fill. Both call for a decision: delete it or write a rule that fills it.

A year-end consistency read

List the rows marked published but missing a delivery date, rows whose label was never verified and disputes still open. These are half-finished jobs to close before the year ends. Doing this before you meet the accountant shortens the meeting.

Version notes and the archive

At the end of the review, archive the table under a year-end name and open a clean copy for the new year. Write field changes in a version note. Give the archived file read-only access.

Example Template: A Sponsored Content Revenue Record Table (Hypothetical)

No real record sits in this sample; it was made up to show the layout. Party names, codes and amount placeholders describe no real person or company; you will enter your own values in the amount column.

Row S-02 has an empty verification cell, which means nobody has yet confirmed that the disclosure and rel value are live on the page. Row S-03 is in dispute and stays open until its outcome is written. T-01, T-02 and T-03 are hypothetical placeholders. Before using the table, run through these points:

• Does the status column use only values chosen in advance?
• Does every published row have a verification date?
• Can only authorised people open the amount column?
• Is personal data in the party column limited to what is needed?

When a new sponsored job arrives, the record moves through these steps:

1. A row is opened with the request date and the party.
2. The type and the label decision are added to the row.
3. After publication the label and rel value are checked on the live page.
4. A closing reason is written and the status is updated.

Frequently Asked Questions

How do you record sponsored content revenue?

Keep each sponsored piece on its own row: request, approval, publication and closing dates, party, line item type, disclosure and rel details, and status. Use fixed pick-list values for type and status. Questions about tax and declarations should be listed and taken to an accountant rather than answered inside the log.

Why keep sponsored content revenue apart from ad revenue?

Ad revenue is mostly a repeating stream, whereas each sponsored piece is a separate agreement with its own text and label. Kept apart, it is easy to read later whom a piece belonged to, how it was marked and when it closed, with none of that detail lost inside a total.

Which fields should the record include?

A record code, type, party, four dates (request, approval, publication, closing), page address, the disclosure shown to readers, the link's rel value, a verification date, status and an amount field. Only authorised people should see the amount field. More columns can be added when a need appears.

Who should I ask about tax questions?

Ask an accountant or another qualified adviser about tax, declarations and business status. This article offers no advice on them. A tidy log helps the conversation, because date, party, type and amount are organised and ready to export.

Why does the record include disclosure details?

How a sponsored piece was marked is a fact that may be questioned later. The disclosure wording and the rel value on the row show what you decided at the time. Google's publisher guidance expects sponsorship to be stated clearly, and the record helps you document that you followed the principle.

How often should the log be reviewed?

Check new and still-open rows at each month end, and review the structure of the table once a year. Remove unused columns, close half-finished items and archive the table. Writing field changes into a version note keeps it readable later why anything changed.

Conclusion and Next Step

The whole approach rests on one principle: a sponsored piece lives on its own row, with its own dates and its own label details. To keep the table from wearing you out as rows pile up, build the fields from pick-list values at the start, put the annual review on the calendar and leave tax questions to an accountant. The log neither earns nor predicts income; it makes what was done readable afterwards.

For the other end of a sponsored piece, the buyer's side, the guest post page on Akua shows current listings. The buyer's path is short: choose a listing, add it to the basket and pay; once the seller accepts, work begins, a delivery notice arrives when it is finished, and a dispute can be opened if the result differs from the listing. For publisher terms and figures, look only at the pricing policy page on the site; this article gave no information on income, commission or payment timing.