Please enable JavaScript to view this site.

Navigation: Schema: Contacts > Tables

ListCampaignStatisticsByListId: Sendinblue List Campaign Statistics by List ID

Get a list's details

Catalog: Sendinblue

Schema: Contacts

Label: List Campaign Statistics by List ID

This is a read-only table function. The Sendinblue API may not support changing the data or the Invantive UniversalSQL driver for Sendinblue does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Sendinblue API.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function ListCampaignStatisticsByListId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

listId

int64

 

Id of the list

 

Columns of Table Function

The columns of the table function ListCampaignStatisticsByListId are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

campaignId

int64

Campaign ID

ID of the campaign

createdAt

datetime

Creation Date

Creation UTC date-time of the list (YYYY-MM-DDTHH:mm:ss.SSSZ)

dynamicList

boolean

Dynamic List

Status telling if the list is dynamic or not (true=dynamic, false=not dynamic)

folderId

int64

Folder ID

ID of the folder

id

int64

ID

ID of the list

name

string

Name

Name of the list

stats_clickers

int64

#Clickers

Number of total clicks for the campaign

stats_complaints

int64

#Complaints

Number of complaints (Spam reports) for the campaign

stats_deferred

int64

#Deferred

Number of deferred emails for the campaign

stats_delivered

int64

#Delivered

Number of delivered emails for the campaign

stats_hardBounces

int64

#Hard-bounces

Number of harbounce for the campaign

stats_listId

int64

List ID

List Id of email campaign (only in case of get email campaign(s)(not for global stats))

stats_returnBounce

int64

#Return-bounces

Total number of non-delivered campaigns for a particular campaign id.

stats_sent

int64

#Sent

Number of sent emails for the campaign

stats_softBounces

int64

#Soft-bounces

Number of softbounce for the campaign

stats_trackableViews

int64

#Trackable Views

Recipients without any privacy protection option enabled in their email client

stats_uniqueClicks

int64

#Unique Clicks

Number of unique clicks for the campaign

stats_uniqueViews

int64

#Unique Views

Number of unique openings for the campaign

stats_unsubscriptions

int64

#Unsubscriptions

Number of unsubscription for the campaign

stats_viewed

int64

#Viewed

Number of openings for the campaign

totalBlacklisted

int64

Total Blacklisted

Number of blacklisted contacts in the list

totalSubscribers

int64

Total Subscribers

Number of contacts in the list

 

10-06-2024 19:02 Version 24.1.3-BETA+4689

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer