Welcome to maxclicks 101

maxclicks brings customer data, AI agents and email into one workspace. You give maxinja the campaign or journey brief; it builds from the records, audience definitions and brand guidance you supply. Your team can inspect the resulting audience, email and workflow before putting them into use.

Use this course to understand how the service fits your marketing operation, what your team controls, and where a developer connects your source systems. Each lesson explains the decisions behind a feature before the setup steps.

What maxclicks does

A customer record becomes useful when it changes who you contact, what you say or when you act. Four connected capabilities make that possible:

• You decide what you track. Set up schemas for your contacts, for the things around them like products and orders, and for the events they trigger. A field is either saved on the record or worked out on demand.
• You direct the agents. Describe an audience, calculation, campaign or journey. maxinja generates the definitions and content in their supported app surfaces; inspect the saved result and refine the brief.
• Customer context changes the message. Liquid inserts known values; Adaptyle writes the passages you mark using selected data and brand context. Keep essential prices, dates and links in fixed content.
• Automation reacts to your data. Workflows run when an event fires or a record changes.

Your team builds campaigns and journeys in the app. Developers use the REST API to maintain records, supply events, trigger supported sending operations and read results. Email is the available communication channel.

From customer context to campaign

Consider a coffee business introducing a new single-origin coffee. Purchase records can identify returning customers. A saved segment selects those with at least two orders and no recent purchase. The email keeps the product, price and destination link fixed while Adaptyle adapts the introduction for a pour-over customer, an espresso customer or someone buying a gift.

The work remains inspectable: source records, matching contacts, selected fields, generated samples and delivery results. The personalization guide uses real generated previews from the fictional Halden demo to show that connection.

Two ideas to get first

You shape the data. A schema is like a form, an attribute is a question on that form, and a record is one filled-out copy. If a spreadsheet is a clearer picture: a schema is a table, an attribute is a column, and a record is a row. You define the questions once, and every contact, product, or order is another copy.

You describe conditions instead of writing code. When you want a segment like "customers who bought in the last 30 days but haven't opened an email since," you write that sentence. maxinja produces a human-readable description you review, plus a hidden expression that runs it. You read English, not SQL.

That second idea gives you the evaluated attribute: a field worked out when you need it, like "the company this contact works for" or "total spend last quarter." You write the sentence, maxinja builds the field. The data model lesson covers this in depth.

The lessons

How to work through it

The lessons run in order: setup, then your data, then your audience, then content and sending, then automation, then the supporting topics. Each one explains why before how, and links to its full reference page when you want the detail. Read them in order the first time, then come back to whichever one you need.

Next

Get oriented in your space: see where contacts, schemas, segments, email, and workflows live.