A CSV field guide for indexing campaigns

Use fields with one meaning

Store referring_url and destination_url separately. Add campaign_id, published_at, selected_mode and baseline_status. Use an explicit unknown value when a status has not been checked rather than leaving a blank that might be read as failure.

Record timestamps consistently

Choose one timezone for machine records and include it in the field name or value. Keep submitted_at, processed_at and observed_at separate. If you import an external report, retain its original timestamp rather than replacing it with the time you opened the file.

Preserve evidence and privacy

Keep private notes and supplier credentials out of shared client exports. Retain the underlying observation source for an internal audit. A compact client report can summarize results while the detailed ledger explains exactly which URLs, checks and costs produced those totals.

Put the guide to work

Create a dated campaign note with the objective, the eligible URLs and the next review date. Follow the related guide below for the next step, then consult the RalfyIndex documentation for service-specific actions.

Sources and scope

Service descriptions are based on the linked public pages reviewed 8 November 2026. Practical workflows are original editorial guidance. Provider claims have not been independently benchmarked here.

• RalfyIndex: features and credit packs
• RalfyIndex: processing modes
• RalfyIndex: terms and refund policy

Continue with the next task

These are related promotional properties in the same RalfyIndex reference collection. They are not independent endorsements.