AI Content Personalizer For WordPress

How To Use & Features

1) Introduction

1.1 What this plugin does

AI Content Personalizer helps you track visitors, build profiles, classify users into segments, assign lead scores, and apply personalized experiences based on rules and block-level logic. It combines behavioral tracking, audience grouping, and conditional rendering so your site can show more relevant content.

• Tracks both anonymous and known visitors (according to settings and consent).
• Builds visitor activity timelines for analysis.
• Lets you define segments by attribution, behavior, form events, and scoring data.
• Runs personalization rules for targeted content delivery.
• Supports AI-assisted workflows with OpenAI/Gemini when API keys are configured.

2) Concepts and How the Plugin Fits Together

2.1 Visitor vs Contact

A visitor is anyone whose request is tracked by the plugin. A contact is a richer profile record (often after form submission and mapping). A contact can accumulate segment membership and lead score over time.

2.2 Segments

Segments are named audience definitions. They are used for analytics, filtering, and targeting. Example: “UTM Source = linkedin” or “Lead score above threshold”.

2.3 Rules

Rules define when personalization applies. A rule can include one or more conditions and optional controls (priority, status, scheduling, etc. depending on build).

2.4 Lead score

Lead score reflects engagement quality based on your scoring rules. Dashboard surfaces this value for quick prioritization and filtering.

2.5 Known vs anonymous lifecycle

Anonymous tracking allows early behavior capture. Field mapping and form capture gradually convert anonymous visitors into known profiles.

2.6 Locate admin menu

Submenu	Purpose
Dashboard	KPIs and lead overview
Rules	Personalization rules and categories
Segments	Audience definitions
Lead Scoring	Scoring rules
Visitors Profile	Events, profiles, export
Global Settings	Privacy, consent, security, AI settings
License	License activation and status
Logs	Debug logs (visible when debug enabled)
Help & Support	FAQ and support resources

3) Dashboard

3.1 Dashboard purpose

The Dashboard provides operational visibility for current traffic, active personalization, and lead quality trends.

3.2 KPI widgets

• Total Visitors (Today): Total + known/anonymous split.
• Active Personalization Rules: Active rule count and experiments count.
• High-Value Leads: Weekly count above threshold shown in UI.

3.3 Lead Dashboard

Use filters to quickly narrow leads by score interval, segment, and search text. Score intervals follow AI Settings range and are translated into actual numeric filtering behind the scenes.

1. Select score range from dropdown.
2. Optionally pick segment.
3. Search by name/email.
4. Review live-updated table results.
5. Use Reset Filter to clear all conditions.

3.4 Additional dashboard panels

Lower sections include analytics charts and insight tabs for ongoing optimization.

• Visitor Segments Distribution chart
• Lead Score Distribution chart
• Visitor Analysis trend chart
• Top Personalization Insights tabs for Rules, Segments, and Visitors Profile

Use the dashboard date-range picker to refresh chart and activity context for a selected period.

4) Global Settings

Path: AI Content Personalizer → Global Settings.

This module controls privacy, consent, tracking, AI/security integration, template customization, field mapping, and debug behavior. Configure this section before rolling out broad personalization.

4.1 Privacy

• Set anonymous data retention period.
• Set known visitor retention period.
• Save and confirm success notice.

Align values with legal/compliance policy and internal data minimization standards.

4.2 User Consent

• Enable/disable consent popup.
• Set re-prompt interval policy.
• Save and verify front-end behavior in private window.

4.3 Visitor Profiles

• Control anonymous visitor tracking toggle.
• Save changes and validate with test sessions.

4.4 Lead Scoring & Activity Tracking

4.4.1 Page visit scoring restriction

Use page visit scoring restriction to prevent repetitive page refreshes from inflating lead score unrealistically.

• Immediately (no restriction)
• 1 hour / 6 hours / 12 hours / 24 hours / 7 days
• Only once per contact

4.4.2 Suggestion Sources (Post Types)

Choose which public post types AI scoring suggestions can use.

• Posts and Pages remain required.
• Additional public post types can be toggled.

4.5 Security (LLM + REST key)

4.5.1 LLM configuration

1. Select platform (OpenAI/Gemini).
2. Select model.
3. Enter API key.
4. Click Test Connection.
5. Save settings.

Use status indicators (Connected/Error/Disconnected) to verify readiness.

4.5.2 WordPress REST API key

1. Generate or regenerate key.
2. Copy securely.
3. Rotate immediately if exposed.

4.6 AI Settings

• Configure high-intent pages.
• Configure high-intent countries.
• Add Business Information context for AI.
• Configure lead score min/max range as needed.
• Save AI Settings.

Lead score min/max is used by AI scoring suggestions and dashboard lead-score interval filters.

4.7 Customize Templates

Use this section to style plugin-generated templates without code changes.

4.7.1 AI Analysis Email Template

• Header/footer background color
• Outer background color
• Reset to defaults and save controls

4.7.2 CSV Export Email

• Accent color
• Outer background
• Info/footer background
• Message panel background

4.7.3 Consent Popup

• Overlay tint and panel background
• Title/body text colors
• Accept/Decline button styles
• Heading and description copy

4.8 Field Mapping

Map form fields to profile attributes (first name, last name, email, phone, website, etc.) for consistent identity enrichment.

1. Select form source.
2. Choose profile field type per row.
3. Select matching form field.
4. Add/remove rows as needed.
5. Save Field Mapping.

4.9 Debug Mode

• Enable only during diagnostics.
• Logs menu appears when enabled.
• Disable after issue is resolved.

5) Segments

Path: AI Content Personalizer → Segments.

5.1 Segment list

Use list screen to review segment definitions, search segments, and perform actions like view/edit/delete.

5.2 Create a segment

1. Click Add New.
2. Enter name.
3. Select segment type (core or UTM type).
4. Complete dynamic fields for selected type.
5. Save segment.

Keep segment names descriptive (for example: UTM-LinkedIn-TOFU, LeadScore-Above-500).

5.2.1 Segment types

• Lead Score: Segment visitors by score threshold/range.
• Location: Match visitors by country/location data.
• Post Type: Include visitors who interacted with a specific post type.
• Query String: Match URL query parameters.
• Referred From: Match referrer source/domain.
• Submitted Form: Include visitors who submitted a selected form.
• Taxonomy: Match visits tied to category/tag/custom taxonomy context.
• Visited Page: Include visitors who visited selected pages/URLs.
• UTM Source: Segment by utm_source value.
• UTM Medium: Segment by utm_medium value.
• UTM Campaign: Segment by utm_campaign value.
• UTM Term: Segment by utm_term value.
• UTM Content: Segment by utm_content value.

5.3 View/Edit segment

View details for validation. Edit to refine targeting as campaign needs evolve.

6) Rules (Personalization)

Path: AI Content Personalizer → Rules.

Rules are the execution layer of personalization. They connect audience conditions to behavior/output decisions.

6.1 Rules vs Categories tabs

• Rules: create and manage personalization logic.
• Categories: classify rules by campaign/team/use-case.

6.2 Create rule workflow

1. Click Create.
2. Enter rule name and description.
3. Add condition rows and operators.
4. Set optional controls (priority, scheduling, experiment mode as available).
5. Save and test.

6.3 Rule actions

• Edit for refinements.
• Deactivate to pause safely.
• Delete when fully obsolete.

6.4 Condition types reference

Each rule condition type is used for a specific targeting dimension:

• Visitor country: Match visitors from selected countries.
• Logged-in user: Target logged-in or logged-out users.
• Time elapsed / New visitor: Target based on session age or first-time visit behavior.
• User's last visit: Match users by recency of previous visit.
• Visiting time / Specific visiting time: Target by current time window.
• Device type: Target desktop/tablet/mobile visitors.
• Browser language: Match visitor language/locale.
• User role: Target specific WordPress roles.
• User meta: Target by user profile metadata values.
• Visiting date / Visiting day: Target by date-based schedules (specific days/dates).
• Query string: Match URL query parameters.
• Referrer: Match traffic source/referring URL.
• Cookie: Match custom cookie presence/value.
• UTM campaign/content/medium/source/term: Target by marketing attribution parameters.
• Completed form submission: Target visitors who completed selected forms.

Each type exposes its own operators and value fields in the rule builder.

6.5 Best practices

• Use specific conditions first, then broaden gradually.
• Avoid overlapping high-priority rules unless intentional.
• Use naming conventions and categories for maintainability.
• Retest after every edit on real-like traffic scenarios.

7) Lead Scoring

Path: AI Content Personalizer → Lead Scoring.

Lead scoring converts behavior into a numeric qualification signal used in Dashboard and profile workflows.

7.1 Rule types

• Page: scoring on page-based actions.
• Form: scoring on form submission events.

7.2 Create scoring rule

1. Click Add New.
2. Name rule.
3. Select type.
4. Select target item (page/form).
5. Set score delta.
6. Save.

Use cooldown settings in Global Settings to prevent score inflation from repeated quick actions.

7.3 AI Scoring tab

The AI Scoring tab includes filter and action controls to run score generation safely and predictably.

7.3.1 Type-selection checkboxes

• All types checkbox selects/deselects every available type.
• Individual type checkboxes let you include only selected content types (for example Pages, Posts, or Forms).
• Type badges typically show item counts so you can estimate how many records may be processed.
• Generate Scores button remains disabled until at least one type is selected.

7.3.2 Include generated checkbox

• Include generated scored page/post/forms controls overwrite behavior.
• When unchecked, generation targets only items without existing generated AI score.
• When checked, already generated items are included again and scores may be replaced.
• A warning message appears before overwrite-style runs so users avoid accidental re-generation.

7.3.3 Generate Scores button (batch run)

• Runs a batch AI scoring job for selected types.
• Uses current AI score range and business context from Global Settings.
• Should be used after confirming type selection and include-generated setting.
• During processing, button and related controls may show disabled/loading states until completion.

7.3.4 Content scores listing actions

• Table combines supported content records and integrated form records.
• Use search, sorting, and content-type filters to narrow rows before running actions.
• Per-row controls allow generating or refreshing AI score for an individual item.
• Batch actions are best for initial setup; row-level actions are best for targeted updates.

7.3.5 AI score suggestions during rule creation

Generated AI scores are also surfaced as suggestions while creating a Lead Scoring rule.

• When you type/search and select a page, post, or form by name, the system can suggest an AI score for that selected item.
• Use the suggested value as a starting point, then adjust manually if needed based on campaign context.

If LLM is not configured, AI Scoring shows a setup notice linking to Global Settings security controls and generation buttons remain unavailable.

8) Visitors Profile

Path: AI Content Personalizer → Visitors Profile.

8.1 Tabs

Tab	Purpose
Recent Events	Chronological event stream
Visitor Profiles	Searchable contact records
Data Export	Export workflow

8.2 Recent Events

Inspect event flow quality and timing. Use this for troubleshooting tracking gaps.

8.3 Visitor Profiles list

Search by known data points and open contact details for full timeline review. Also columns can be selected dynamically by clicking on the Columns button

 

8.4 Profile detail view

8.4.1 Identity and score summary

Shows core profile identity fields and current lead score at a glance. Use this block first to confirm you are reviewing the correct visitor and to quickly assess priority level.

8.4.2 Segment memberships

Lists audience segments currently matched by the profile. Use this to validate targeting logic and understand why a visitor is receiving specific personalized experiences.

8.4.3 Activity timeline

Displays chronological events (page views, form interactions, and related activity signals). Use it to reconstruct user journey and diagnose scoring or personalization outcomes.

8.4.4 AI analysis (individual profile)

1. Click on Analyze Now button to generate AI analysis.
2. Review the AI analysis report.
3. you can also send the AI analysis report to a specific email address by entering the email address in the email input field and clicking on the Send AI Analysis Report button.

Provides AI-assisted interpretation of profile behavior and engagement context (when enabled/configured). Use this for faster insight extraction before manual follow-up decisions.

8.4.5 Business value record (Convert To Customer)

• Captures qualification-oriented context for sales/marketing prioritization. Use it to map behavioral data into practical business action (high-value follow-up vs nurture).
• once user is converted to customer, they will be marked as converted and their tracking will permanently disabled.

8.4.6 Tracking status controls

Profile-level tracking controls (such as activate/deactivate tracking, where available) admins can use to manage future data capture for specific records based on operational or compliance needs.

8.5 Data export

1. Open Data Export tab.
2. Set filters/date range/format.
3. Run export.
4. If email is provided, a download link will be mailed to the provided email address.

9) Block Editor (Gutenberg) Personalization

9.1 What it does

The plugin can store personalization conditions directly in block metadata and evaluate them during front-end block rendering.

9.2 Configure block conditions

1. Edit post/page in block editor.
2. Select target block.
3. Open AI Content Personalizer panel in sidebar.
4. Define visibility/personalization conditions.
5. Update post and verify on front end.

Rules can be selected directly in Gutenberg block personalization controls.

9.3 Rewrite with AI (Gutenberg)

Supported text blocks can use Rewrite with AI from block toolbar.

• Improve Current Content: refine selected block text (prompt optional).
• Generate Content: create new block content from prompt (prompt required).

1. Select a supported text block.
2. Click Rewrite with AI.
3. Choose mode and add prompt if needed.
4. Generate and review output.
5. Apply with Replace block text.

Requires configured LLM credentials in Global Settings.

10) Advanced Custom Fields (ACF) Integration

When ACF is installed and detected, integration components load in admin and front contexts.

• Admin integration supports ACF-linked configuration surfaces where available.
• Front integration supports ACF-backed personalization behavior where configured.

10.1 AI Assist in Classic/ACF editing

Classic/ACF editing flows provide AI Assist (Rewrite with AI) for supported field types such as text, textarea, and wysiwyg fields.

• Improve Current Content: prompt optional.
• Generate Content: prompt required.

1. Open post/page where ACF fields are present.
2. Click AI Assist on a supported field.
3. Choose mode, run generation, and apply output.
4. Can reference other fields by using @field_name in the prompt.
5. Click on the Update button to update the field with the generated content.

Requires configured LLM credentials in Global Settings.

10.2 Rules selection in Classic/ACF

Rules selection is available in the Personalize ACF Field Group modal, along with segments, lead score, user role, specific users, and show/hide outcome.

 

10.2.1 Important note for Time elapsed rule in Classic templates

For Time elapsed / Time on current page behavior in Classic/ACF frontend rendering, your template should use the plugin wrapper helper functions. Without these wrappers, delayed visibility logic may not render as expected in some theme structures.

 

10.2.2 Normal ACF group/repeater rendering (required wrapper pattern)

Wrap your group output using:

• aicpw_acf_group_start( $post_id, $selector )
• aicpw_acf_group_end()

Example:

<?php aicpw_acf_group_start( get_the_ID(), 'your_field_name_or_key' ); ?>
  <?php // render ACF group/repeater content here ?>
<?php aicpw_acf_group_end(); ?>

 

10.2.3 Flexible Content layout rendering (layout-level time rule)

When using Flexible Content and applying time-based rules at layout level, open the layout section with:

• aicpw_acf_fc_group_start( $post_id, $flex_selector, $layout_name )
• and close with aicpw_acf_group_end()

Example inside a have_rows() loop:

<?php while ( have_rows( 'flexi' ) ) : the_row(); ?>
  <?php aicpw_acf_fc_group_start( get_the_ID(), 'flexi', get_row_layout() ); ?>
    <?php // render layout block content here ?>
  <?php aicpw_acf_group_end(); ?>
<?php endwhile; ?>

 

10.2.4 Implementation checklist

• Always keep start/end wrappers balanced.
• Use correct field selector (name/key) for normal groups.
• Use actual flexible field selector + exact layout slug for flexible layouts.
• Test delay behavior on frontend as anonymous and known visitor contexts.

If no time-based rule applies, these helper calls are safe no-ops and do not break rendering.

11) Front-End Behavior (Tracking and Consent)

11.1 Tracking script behavior

Plugin scripts record activity through REST endpoints, subject to consent and settings. Validate that optimization/caching tools do not remove essential scripts for anonymous users.

11.2 Consent popup

• If enabled, users may be gated by consent interaction before full tracking logic runs.
• If user decline consent, the user will not be tracked and will not able to see personalized content. it will again asked for consent after the admin decided time-period (Global Settings → Privacy & Tracking → User Consent Management → Consent Re-prompt Interval).
• Consent popup styling and messaging can be customized in Global Settings → Customize Templates → Consent Popup.

11.3 Forms and identity enrichment

Form tracker + field mapping converts event-only visitors into richer known profiles over time.

12) Logs

12.1 Enable logs

1. Go to Global Settings → Debug Mode.
2. Enable debug and save.
3. Open Logs menu.

12.2 Safe log handling

• Logs may contain URLs, errors, request metadata.
• Redact tokens/secrets before sharing.
• Disable debug after diagnosis.

13) Help and Support

Path: AI Content Personalizer → Help & Support.

14) Deactivation, Data Removal, and Uninstall

14.1 Deactivation feedback

You will be prompted with a feedback modal during deactivation. This is optional and does not replace backup/cleanup planning.

14.2 Optional destructive cleanup

If uninstall cleanup option is checked, plugin data tables/options will be removed. Treat this as destructive operation and confirm backup before proceeding.

18) Troubleshooting

18.1 Always redirected to License

Cause: inactive/invalid license.
Fix: reactivate license and verify external connectivity.

18.2 AJAX save errors (license_inactive/403)

Activate valid license first; protected AJAX endpoints are blocked otherwise.

18.3 LLM test connection fails

• Verify API key.
• Verify model/platform compatibility.
• Check billing and outbound HTTPS firewall rules.
• Check server clock accuracy.

18.4 No visitors/profiles showing

• Anonymous tracking enabled?
• Consent flow blocking events?
• Caching/optimization stripping scripts?
• Testing affected by ad blocker?

18.5 Blocks always visible/hidden

• Verify block-level condition config.
• Verify visitor context for rules.
• Purge caches and retest.

18.6 Logs menu missing

Enable Debug Mode under Global Settings.