Understand Campaigns

​

Overview

A campaign is the operational scope in which GetBill organizes and tracks a set of receivables. It connects imported receivables, the collection timeline applied to them, synchronization history, and collection results. A GetBill campaign is not a marketing campaign or a one-off email send. It persists across multiple imports or snapshots so the same receivables scope can be tracked over time.

​

Distinguish the concepts

A campaign can receive multiple successive imports. Depending on its synchronization mode, GetBill interprets receivables omitted from the new import differently.

​

Choose the synchronization behavior

The mode belongs to the campaign or configured flow. It does not vary from row to row.

​

Authoritative synchronization (full_sync)

Each valid import or snapshot represents the campaign’s complete current scope:

• a new stable reference creates a debt
• a known reference updates its debt
• a previously known debt that is omitted is treated as settled outside GetBill
• a debt that reappears can resume or restart its timeline depending on its progress.

The general Campaign Snapshots API supports only this mode.

​

Incremental updates (status_sync)

Each import contains only debts to create or update. An omitted debt remains unchanged. The Statut column is optional and does not define this behavior: a present row can create a debt, change its balance, or change its status. This mode is available for campaign imports and SFTP flows, but not through the general Campaign Snapshots API. See SFTP integration profiles for the detailed rules of both behaviors.

​

Understand the lifecycle

An API-referenced campaign must be active and associated with a timeline before it can receive a snapshot. Its API reference identifies the campaign permanently even if its display name changes.

​

Automatic monthly SFTP campaigns

An SFTP integration can use one fixed campaign or automatic monthly campaigns: On the first synchronization for a month, GetBill creates or reuses the SFTP campaign identified for the company, flow, and month in YYYY-MM format. Its name generally follows Flow name - 2026-07. When created, it receives the workflow and synchronization mode configured for the flow. The month is the calendar month of the run in the configured time zone. It is not derived from the filename, the SFTP modification time, or dates contained in the rows. For example, a file relating to June but processed on July 1 feeds the July campaign. This organization creates distinct monthly cohorts for tracking and reporting. Later synchronizations in the same month reuse that campaign with its original workflow and mode instead of creating another one. Changing the flow’s default workflow later does not change the workflow of a monthly campaign that already exists; the new workflow applies when a future monthly campaign is created. Creating a campaign for a new month does not automatically complete previous campaigns. They remain available for monitoring and reporting. It also does not necessarily create a new debt record: GetBill uses stable references to find debts it already knows and retain their history. Monthly creation is idempotent: GetBill ensures that the campaign for the month exists without creating another one on every run. It does not mean that a new import runs without a file or without the scheduled SFTP flow being executed.

​

Next steps