ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Loader Magnews Audience

Magnews Audience is a powerful audience management platform that enhances customer engagement through targeted and personalized communication strategies. Its primary function is to consolidate and analyze customer data from various sources, providing marketers with valuable insights into customer behavior, preferences, and interactions.

Business value in CDP

By utilizing Magnews Audience as a loader, marketers can optimize their marketing campaigns, delivering highly personalized content and experiences to specific audience segments based on the rich data imported from the CDP. This streamlined data transfer process not only enhances efficiency but also empowers marketers to create targeted campaigns that resonate with their audience, ultimately driving greater customer satisfaction and loyalty.

Setting up the loader in MI

This component is used for importing contacts to the MagNews EDM tool.

Learn more: about magnews API documentation here.

Data In/ Data Out

Data In

Loader requires imports.csv file in directory /data/in/tables/imports.csv


File structure:  

/data/in/tables/imports.csv file must contain two columns:

  • NOME_UTENTE (required)- unique contact ID
  • EMAIL (required) - contains email address

Example:  


NOME_UTENTE

EMAIL

4321

john.doe@email.com

1234

jane.doe@email.com

1111

foo@bar.com

Data Out

N/A

Parameters

Username (required)

The username used for the MagNews platform.
Customer_id (required)

The user’s ID in the Magnews platform. This can be found in the user’s profile under Account Information.  

  

Screenshot 2022-02-21 at 7.19.20 PM.png

  

  
Access_token (required)

The secret key provided by MagNews for registered application. This can be found in Management > System > Digital Certificates.

Screenshot 2022-02-21 at 7.19.31 PM.png
WSDL (required)

WSDL document with all MagNews SOAP API endpoints. CanIt can be found in MagNews API documentation.

Screenshot 2022-02-21 at 7.19.41 PM.png

  

  

Audience

Database_id (required)

ID of database where contacts are stored.

Audience_id (*)

The ID of the audience where contacts from imports.csv file will be imported.

Audience_name (*)

Name of newly created audience.

Remember: At least one audience_id OR audience_name must be provided.

Example:  

{
  "parameters": {
    "credentials": {
      "username": "username",
      "customer_id": "1234",
      "#access_token": "###",
      "wsdl": "https://foo.bar/wsapi?wsdl"
    },
    "audience": {
      "database_id": "42",
      "audience_id": "84",
      "audience_name": "foo"
    }
  }
}

Methods

  • When audience_id is provided in the configuration. The component will check audience_id existence and import all given contacts there.
  • When audience_id is unknown audience_name must be provided in the configuration. The component will create a new audience with defined audience_name and import all given contacts to the newly created audience.

 

Back to top