> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/guides/quick-guides/create-your-first-campaign/campaign-setup/attack-settings.md).
# Attack Settings
Next, define the Campaign and Attack settings, then link the relevant Awareness Training.\
\
**3.1** Campaign settings:\
\
Specify the campaign name, associated client, and additional options in this section.
**3.2** Attack Settings:
Next, we will specify the parameters for the Attack.\
\
**Domain** -> Select the attack domain registered in [step 2](/guides/quick-guides/create-your-first-campaign/register-an-attack-domain.md) of the Quick Guides. This will be the primary domain for the email address and the associated landing page.
**SSL** -> Lucy seamlessly integrates with Let's Encrypt to automatically create, validate, and bind SSL certificates to your domain.
What is SSL?
SSL (Secure Sockets Layer) acts as a protective shield. It ensures that data exchanged with the phishing page remains secure and protected from eavesdropping. This safeguard helps maintain the realism and safety of your simulation.
Without an SSL certificate, recipients will see a red warning page, indicating an insecure site. This can undermine the authenticity of your simulation.
**Sender Name**, **Email**, and **Subject** -> Define the sender of the attack, their email address, and the subject.
{% hint style="warning" %}
Using a sender email that matches your registered domain is recommended. This improves email deliverability by leveraging existing DNS records and reduces the risk of emails being flagged as spam.
{% endhint %}
**3.3** Editing the Email Content:\
\
The Lucy email editor is a versatile tool that lets you tailor email content to your preferred language and structure. Most templates include variable placeholders like **%name%**, which auto-insert each recipient's name for a personalized touch, making spear-phishing attacks more effective.
{% hint style="warning" %}
The objective of simulated attacks is to persuade users to click on an email link, enabling the collection of click-through statistics.
{% endhint %}
To add a **new** link in your email, highlight the desired word or phrase, click the link icon, and enter **%link%** in the URL field.
{% hint style="info" %}
The `%link%` placeholder automatically generates a URL combining your registered attack domain with a unique tracking hash for each recipient, allowing for detailed tracking.
For example, with "open-ai.net" as the domain, the recipient sees a link like "[https://open-ai.net/xvcskahjry](https://open-ai.net/xvcskahjry)", enabling precise monitoring of individual interactions.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.lucysecurity.com/guides/quick-guides/create-your-first-campaign/campaign-setup/attack-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
