Please enable JavaScript to view this site.

Made in EU
ActiveCampaign Forums

Navigation: Catalog: ActiveCampaign > Schemas > Schema: Views > Views

ContactGeoIps: ActiveCampaign Contact Automations

Catalog: ActiveCampaign

Schema: Views

Label: Contact Automations

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

View Columns

The columns of the view ContactGeoIps are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

campaignid

int64

 

 

contact_adate

datetime

 

 

contact_bounced_date

datetime

Bounced Date

 

contact_bounced_hard

int64

Bounced Hard

 

contact_bounced_soft

int64

Bounced Soft

 

contact_cdate

datetime

Created

 

contact_deleted

int64

Deleted

 

contact_edate

datetime

 

 

contact_email_domain

varchar2

 

 

contact_email_local

varchar2

 

 

contact_email

varchar2

Email Address

 

contact_firstName

varchar2

First Name

 

contact_gravatar

int64

Gravatar

 

contact_hash

varchar2

Hash

 

contact_id

int64

ID

 

contact_ip

int64

IP Address

 

contact_lastName

varchar2

Last Name

 

contact_organization

int64

Account

Deprecated. Do not use.

contact_orgid

int64

Organisation ID

 

contact_phone

varchar2

Phone

 

contact_rating_tstamp

datetime

Rating Date

 

contact_segmentio_id

int64

 

 

contact_sentcnt

int64

 

 

contact_socialdata_lastcheck

datetime

Social Data Last Check

 

contact_ua

varchar2

 

 

contact_udate

datetime

Last Updated

 

contact

int64

Contact

 

geoAddress

int64

 

 

geoaddrid

int64

 

 

id

int64

ID

 

ip4

varchar2

IPv4 Address

 

messageid

int64

 

 

tstamp

datetime

 

 

 

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